|
|
|
|
- Overview
- Use
- Use case
- Looping through tables (data files)
Native MariaDB Connector: Specific 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. Native MariaDB Connector: SQLLock and SQLTransaction can be used to manage locks 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. Remark: When reading the next block, the records with items that have the same values as the last record read will not be selected by the query used to fill the "cache". Example: The MariaDB table named "MyTable" contains the following records: | | Record number | Value | ... | ... | 98 | Tata | 99 | Toto | 100 | Toto | 101 | Toto | 102 | Tutu |
The code is as follows: FOR EACH MyTable Trace(MyTable.Value) 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…
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|