That is, you'll have a generic class hierarchy, able to access:
- Any OleDB providers (including latest version of MSSQL, or good old Access/Jet);
- Any ODBC provider (including e.g. MySQL / FireBird);
- Oracle via direct access to the OCI layer;
- and now SQLite3, statically embedded to the executable.
As a result, the SynDBExplorer sample tool is now able to select a SQLite3 database as source, in addition to the OleDB, ODBC or Oracle/OCI database types.
The SynDBExplorer tool is a multi-tabbed software able to list
all tables, and also column names and types - including indexes. It can also
export all result content into csv, json, text or pdf files. And you have some
popup-menus to help you enter field names or values into your SQL
You can download this free tool from this direct link.
As you can see in the SynSQLite3.pas source code, adding such another Database to the SynDB classes model is just a very thin layer, calling the new shared SynSQLite3 unit.
Now I will work on integrating all those SynDB classes into our main framework, which is now named mORMot (at least in the source code).
Feedback and comments are welcome on our forum.