summaryrefslogtreecommitdiffstats
path: root/examples/sql/doc
diff options
context:
space:
mode:
authorVolker Hilsheimer <volker.hilsheimer@qt.io>2023-05-20 14:46:29 +0200
committerVolker Hilsheimer <volker.hilsheimer@qt.io>2023-05-24 17:29:20 +0200
commit8fa28b0cff8f06a7c266f2a6ff2a016daf4ad6d3 (patch)
treec3e06a613076bb2f212840c60aaeb3e64e203db7 /examples/sql/doc
parent84e6d89c1b07830da82da1073930c094f6b99a81 (diff)
Update Cached Table example meta-data
Drop "Example" from the example's title, add SQL instead, and add it to the Input/Output category of examples. It's a documented example, does something meaningful, and looks reasonable. Having one SQL example categorised so that it's easy to see that Qt includes that functionality seems like a good idea. The other examples are mostly small API examples that are still good to have as fully-functional apps rather than just snippets. Pick-to: 6.5 Change-Id: Ib960f38db39c791f7ff5a2b9bf3157ee32b362ec Reviewed-by: Andreas Eliasson <andreas.eliasson@qt.io>
Diffstat (limited to 'examples/sql/doc')
-rw-r--r--examples/sql/doc/src/cachedtable.qdoc3
1 files changed, 2 insertions, 1 deletions
diff --git a/examples/sql/doc/src/cachedtable.qdoc b/examples/sql/doc/src/cachedtable.qdoc
index 35b8fdd440..4b0d3ac1a1 100644
--- a/examples/sql/doc/src/cachedtable.qdoc
+++ b/examples/sql/doc/src/cachedtable.qdoc
@@ -3,8 +3,9 @@
/*!
\example cachedtable
- \title Cached Table Example
+ \title Cached SQL Table
\ingroup sql_examples
+ \examplecategory {Input/Output}
\brief The Cached Table example shows how a table view can be used to access a database,
caching any changes to the data until the user explicitly submits them using a