summaryrefslogtreecommitdiffstats
path: root/doc/man/man3/tqsqlquery.3qt
diff options
context:
space:
mode:
authorTimothy Pearson <[email protected]>2015-03-05 20:59:01 -0600
committerTimothy Pearson <[email protected]>2015-03-05 20:59:01 -0600
commitdfb87398c72e9248aa709ae212e6ab7f2209003d (patch)
tree52422e7b6774fcc503d7c701cb2c77fa016386e8 /doc/man/man3/tqsqlquery.3qt
parent891a448afad4ab1f09bfb0cfee71652975bd7687 (diff)
downloadtqt3-dfb87398c72e9248aa709ae212e6ab7f2209003d.tar.gz
tqt3-dfb87398c72e9248aa709ae212e6ab7f2209003d.zip
Automated update from Qt3
Diffstat (limited to 'doc/man/man3/tqsqlquery.3qt')
-rw-r--r--doc/man/man3/tqsqlquery.3qt8
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/man/man3/tqsqlquery.3qt b/doc/man/man3/tqsqlquery.3qt
index 5cf282d2b..c57e3981a 100644
--- a/doc/man/man3/tqsqlquery.3qt
+++ b/doc/man/man3/tqsqlquery.3qt
@@ -178,9 +178,9 @@ For example:
.PP
To access the data returned by a query, use the value() method. Each field in the data returned by a SELECT statement is accessed by passing the field's position in the statement, starting from 0. Information about the fields can be obtained via QSqlDatabase::record(). For the sake of efficiency there are no functions to access a field by name. (The QSqlCursor class provides a higher-level interface with field access by name and automatic SQL generation.)
.PP
-QSqlQuery supports prepared query execution and the binding of parameter values to placeholders. Some databases don't support these features, so for them Qt emulates the required functionality. For example, the Oracle and ODBC drivers have proper prepared query support, and Qt makes use of it; but for databases that don't have this support, Qt implements the feature itself, e.g. by replacing placeholders with actual values when a query is executed. The exception is positional binding using named placeholders, which requires that the database supports prepared queries.
+QSqlQuery supports prepared query execution and the binding of parameter values to placeholders. Some databases don't support these features, so for them TQt emulates the required functionality. For example, the Oracle and ODBC drivers have proper prepared query support, and TQt makes use of it; but for databases that don't have this support, TQt implements the feature itself, e.g. by replacing placeholders with actual values when a query is executed. The exception is positional binding using named placeholders, which requires that the database supports prepared queries.
.PP
-Oracle databases identify placeholders by using a colon-name syntax, e.g \fC:name\fR. ODBC simply uses \fC?\fR characters. Qt supports both syntaxes (although you can't mix them in the same query).
+Oracle databases identify placeholders by using a colon-name syntax, e.g \fC:name\fR. ODBC simply uses \fC?\fR characters. TQt supports both syntaxes (although you can't mix them in the same query).
.PP
Below we present the same example using each of the four different binding approaches.
.PP
@@ -555,8 +555,8 @@ If you find a bug in Qt, please report it as described in
.BR http://doc.trolltech.com/bughowto.html .
Good bug reports help us to help you. Thank you.
.P
-The definitive Qt documentation is provided in HTML format; it is
-located at $QTDIR/doc/html and can be read using Qt Assistant or with
+The definitive TQt documentation is provided in HTML format; it is
+located at $QTDIR/doc/html and can be read using TQt Assistant or with
a web browser. This man page is provided as a convenience for those
users who prefer man pages, although this format is not officially
supported by Trolltech.