|
|
|
|
|
|
|
|
|
|
- Overview
- Use
- Use case
- Browsing files
MySQL Native Connector: Special 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. For more details, see the documentation about MySQL. 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. MySQL Native Connector The SQLLock and SQLTransaction functions can be used to manage blocks 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 optimizes read operations started with HReadFirst/ HReadNext as well as with the HReadSeekXXX functions. Note Records identical to the last record read (i.e. with identical values in all fields) will not be selected by the read cache fill request for subsequent records. Example In the MySQL table "MaTable", the following records are present: | | | Record number | Value | | ... | ... | | 98 | Tata | | 99 | Toto | | 100 | Toto | | 101 | Toto | | 102 | Tutu |
The code is as follows: FOR EACH MyFile
Trace(MyFile.Valeur)
END
The trace window will display the following values: One record is absent (Record #101 whose value is "Toto").
This page is also available for…
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|