AuroraMiddleware/wxWidgets
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Removed some inappropriate use of verbatim

Browse Source 
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@16130 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Julian Smart 2002-07-10 09:06:56 +00:00
parent ff5802f399
commit 05dedde7d0
1 changed files with 33 additions and 31 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

64
docs/latex/wx/db.tex
View File

@ -1421,7 +1421,8 @@ at least minimal privileges to the table).
\docparam{tableName}{Name of the table on which to check privileges.
{\it tableName} may refer to a table, view, alias or synonym.}
\docparam{priv}{The table privilege being evaluated. May be one of the
following (or a datasource specific privilege):}
following (or a datasource specific privilege):
\begin{verbatim}
SELECT : The connected user is permitted to retrieve data for
one or more columns of the table.
@ -1441,25 +1442,28 @@ following (or a datasource specific privilege):}
example, a unique, referential, or table check
constraint).
\end{verbatim}
}
\docparam{userID}{{\it OPTIONAL.} User for which to determine if the privilege
specified to be checked is granted or not. Default is "".
{\it userID} is evaluated as follows:}
{\it userID} is evaluated as follows:
\begin{verbatim}
userID == NULL ... NOT ALLOWED!
userID == "" ... UserID set equal to 'this->uid'
userID != "" ... UserID set equal to 'userID'
\end{verbatim}
}
\docparam{schema}{{\it OPTIONAL.} Owner of the table. Specify a userID when the datasource
you are connected to allows multiple unique tables with the same name to be
owned by different users. Specifying the table owner makes determination of the
users privileges MUCH faster. Default is NULL. {\it userID} is evaluated as follows:}
users privileges MUCH faster. Default is NULL. {\it userID} is evaluated as follows:
\begin{verbatim}
schema == NULL ... Any owner (DEFAULT)
schema == "" ... Owned by 'this->uid'
schema != "" ... Owned by userID specified in 'schema'
\end{verbatim}
}
\docparam{path}{{\it OPTIONAL.} Path to the table. Default is "".
Currently unused.}
@ -2568,11 +2572,11 @@ by specifying the data in the columns to match on.
To delete all users with a first name of "JOHN", do the following:
\begin{verbatim}
1) Clear all "columns" using wxDbTable::ClearMemberVars().
2) Set the FIRST_NAME column equal to "JOHN".
3) Call wxDbTable::DeleteMatching().
\end{verbatim}
\begin{enumerate}\itemsep=0pt
\item Clear all "columns" using wxDbTable::ClearMemberVars().
\item Set the FIRST_NAME column equal to "JOHN".
\item Call wxDbTable::DeleteMatching().
\end{enumerate}
The WHERE clause is built by the ODBC class library based on all non-NULL
columns. This allows deletion of records by matching on any column(s) in
@ -3264,27 +3268,25 @@ specific function calls.
The requirements of the SELECT statement are the following:
\begin{verbatim}
1. Must return the correct number of columns. In the derived
wxDbTable constructor, it is specified how many columns are in
the wxDbTable object. The SELECT statement must return exactly
that many columns.
2. The columns must be returned in the same sequence as specified
when defining the bounds columns using wxDbTable::SetColDefs(),
and the columns returned must be of the proper data type. For
example, if column 3 is defined in the wxDbTable bound column
definitions to be a float, the SELECT statement must return a
float for column 3 (e.g. PRICE * 1.10 to increase the price by
10%).
3. The ROWID can be included in your SELECT statement as the {\bf last}
column selected, if the datasource supports it. Use
wxDbTable::CanUpdByROWID() to determine if the ROWID can be
selected from the datasource. If it can, much better
performance can be achieved on updates and deletes by including
the ROWID in the SELECT statement.
\end{verbatim}
\begin{enumerate}
\item Must return the correct number of columns. In the derived
wxDbTable constructor, it is specified how many columns are in
the wxDbTable object. The SELECT statement must return exactly
that many columns.
\item The columns must be returned in the same sequence as specified
when defining the bounds columns using wxDbTable::SetColDefs(),
and the columns returned must be of the proper data type. For
example, if column 3 is defined in the wxDbTable bound column
definitions to be a float, the SELECT statement must return a
float for column 3 (e.g. PRICE * 1.10 to increase the price by
10%).
\item The ROWID can be included in your SELECT statement as the {\bf last}
column selected, if the datasource supports it. Use
wxDbTable::CanUpdByROWID() to determine if the ROWID can be
selected from the datasource. If it can, much better
performance can be achieved on updates and deletes by including
the ROWID in the SELECT statement.
\end{enumerate}
Even though data can be selected from multiple tables (joins) in your select
statement, only the base table associated with this wxDbTable object