|
|
|
|
- Overview
- Use
- Use case
- Browsing files
Native MySQL Connector: Specific features
Available only with this kind of connection
The Native MySQL Connector (also called "Native MySQL Access") creates "InnoDB" tables to support locks and transactions on a MySQL database. See the documentation about MySQL for more details. Use case If your server is not configured to support "InnoDB" tables, MySQL automatically creates an ISAM table (default type in MySQL). Refer to the MySQL documentation to learn more more about the server configuration required to support "InnoDB" tables. Native MySQL Connector: SQLLock and SQLTransaction can be used to manage locks and transactions only on MySQL tables of type "InnoDB". If you want to specify another type of table (other than "InnoDB"): - run the CREATE TABLE SQL command
- use the MySQL management tool. In this case, do not use HCreation in your program. HCreation deletes the table ("DROP TABLE" command) if it already exists in order to recreate it.
Browsing files When looping through on a MySQL table, the records are not retrieved all at once but by blocks of 100 records. This value corresponds to a read "cache". This feature is used to optimize the browse operations with HReadFirst/ HReadNext as well as HReadSeekXXX functions. Remark: The items identical to the last record read (which means with identical values for all the items) will not be selected by the query used to fill the "cache" for reading the next records. Example: The following records are found in the MySQL table named "MyTable": | | Record number | Value | ... | ... | 98 | Tata | 99 | Toto | 100 | Toto | 101 | Toto | 102 | Tutu |
The browse code is as follows: FOR EACH MyTable Trace(MyTable.Value) END The trace window will display the following values: One record is missing (Record #101 whose value is equal to "Toto").
This page is also available for…
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|