Lines Matching refs:wxDbTable
4 and \helpref{wxDbTable}{wxdbtable} and their associated functions. These are
8 \subsection{wxDb/wxDbTable wxODBC Overview}\label{wxodbcoverview}
10 Classes: \helpref{wxDb}{wxdb}, \helpref{wxDbTable}{wxdbtable}
75 Datasource connections can have a virtually unlimited number of wxDbTable
107 \helpref{wxDbTable::GetPrev}{wxdbtablegetprev},
108 \helpref{wxDbTable::GetFirst}{wxdbtablegetfirst}, and
109 \helpref{wxDbTable::GetLast}{wxdbtablegetlast}). If the datasource or the
186 \helpref{wxDbTable::GetNewCursor}{wxdbtablegetnewcursor} function. One example
210 not on the wxDbTable instances. This means that if more than one table
517 simpler, the wxDbTable class encapsulates all of the SQL specific API calls
520 The first step in accessing data in a datasource's tables via the wxDbTable
521 class is to create a wxDbTable instance.
524 table = new wxDbTable(db, tableName, numTableColumns, "",
537 Each of the above parameters are described in detail in the wxDbTable
539 parameter - the queryOnly setting. If a wxDbTable instance is created as
541 using this instance of the wxDbTable. Any calls to \helpref{wxDb::CommitTrans}{wxdbcommittrans}
543 connection used by this wxDbTable instance are ignored by this instance. If
544 the wxDbTable instance is created with {\tt !wxDB\_QUERY\_ONLY} as shown above,
548 wxDbTable instance.
550 If a table is to be accessed via a wxDbTable instance, and the table will
554 wxDbTable instance. Also, with some datasources, the number of
557 When defining the columns to be retrievable by the wxDbTable instance, you
568 the number of columns specified when the wxDbTable instance was created
573 makes a call to \helpref{wxDbTable::GetNext}{wxdbtablegetnext} (or any other function that retrieves
576 \helpref{wxDbTable::SetColDefs}{wxdbtablesetcoldefs}
581 (e.g. \helpref{wxDbTable::GetNext}{wxdbtablegetnext},
582 \helpref{wxDbTable::GetPrev}{wxdbtablegetprev}, etc). The variables are not
584 undefined data after a call to \helpref{wxDbTable::Query}{wxdbtablequery}. Only
595 You may have as many wxDbTable instances accessing the same table using the
602 itself. Calling \helpref{wxDbTable::Open}{wxdbtableopen} simply does all the
616 The only reason that a call to \helpref{wxDbTable::Open}{wxdbtableopen} is likely to fail is if the
620 internally in the \helpref{wxDbTable::Open}{wxdbtableopen} function are logged to the error log
679 the default table for the wxDbTable instance.
694 Typically, when an error occurs when calling \helpref{wxDbTable::Query}{wxdbtablequery}, it is a
696 (datasource-specific) reason for what caused the failure of \helpref{wxDbTable::Query}{wxdbtablequery}
701 When the \helpref{wxDbTable::Query}{wxdbtablequery} returns true, the
707 \helpref{wxDbTable::Query}{wxdbtablequery} can take one of two forms. It is
713 uses snapshots and call \helpref{wxDbTable::Refresh}{wxdbtablerefresh}. Most larger brand databases
719 set into the bound memory variables. After \helpref{wxDbTable::Query}{wxdbtablequery}
738 \helpref{wxDbTable::GetNext}{wxdbtablegetnext} is called right after the successful
739 call to \helpref{wxDbTable::Query}{wxdbtablequery}, it actually returns the first record
742 When \helpref{wxDbTable::GetNext}{wxdbtablegetnext} is called and there are
744 \helpref{wxDbTable::GetNext}{wxdbtablegetnext} (as well as all the other
745 wxDbTable::GetXxxxx() functions) will return false.
749 When the program is done using a wxDbTable instance, it is as simple as
752 care of all that is required for cleaning up the wxDbTable instance.
762 Deleting a wxDbTable instance releases all of its cursors, deletes the
765 that the wxDbTable instance was using).
877 \item Does not automatically create the primary index if the 'keyField' param of SetColDef is true. The user must create ALL indexes from their program with calls to \helpref{wxDbTable::CreateIndex}{wxdbtablecreateindex}
899 \item Cannot support selecting for update [\helpref{wxDbTable::CanSelectForUpdate}{wxdbtablecanselectforupdate}]. Always returns false.
900 \item Columns that are part of primary or secondary keys must be defined as being NOT NULL when they are created. Some code is added in \helpref{wxDbTable::CreateIndex}{wxdbtablecreateindex} to try to adjust the column definition if it is not defined correctly, but it is experimental (as of wxWidgets v2.2.1)
980 wxDbTable *table = NULL; // Data table to access
1017 table = new wxDbTable(db, tableName, numTableColumns, wxT(""),
1021 // 'numTableColumns' calls to SetColDefs(), to match the wxDbTable def
1116 // If the wxDbTable instance was successfully created