|
|
|
|
|
|
|
|
|
|
- Overview
- Use
- Use case
- Looping through tables (data files)
MariaDB Native Connector: Special features
 Available only with this kind of connection
The Native MariaDB Connector creates "InnoDB" tables to support locks and transactions on a MariaDB database. See the MariaDB documentation for more details on this type of table. Use case If your server is not configured to support "InnoDB" tables, MariaDB automatically creates an ISAM table (default type in MariaDB). Refer to the MariaDB documentation to learn more more about the server configuration required to support "InnoDB" tables. MariaDB Native Connector: Functions SQLLock and SQLTransaction are used to manage blocks and transactions only on MariaDB tables of type "InnoDB". If you want to specify another type of table (other than "InnoDB"): - run the CREATE TABLE SQL command
- use the MariaDB 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.
Looping through tables (data files) When looping through a MariaDB 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 read record (i.e. with identical values in all fields) will not be selected by the read cache fill request for the following records. Example: In the MariaDB 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…
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|