You are not logged in.
For your information, I've extracted the SQLite3 engine wrapper from SQLite3.pas into the new shared SynSQLite3.pas unit.
It will allow direct access to SQLite3, without our mORMot overhead/features.
For instance, I will create a direct access class following our SynDB hierarchy.
I've also added the function IsSQLite3File() in this new SynSQLite3 unit, which could help you knowing if a file is a valid SQLite3 or not. If it is not, and should be a SQLite3 database file, then it's probably an encrypted version of the file.
Offline
I've also added the SynDBSQLite3 unit, which will interface the SQLite3 engine within the SynDB abstract classes.
That is, you'll have a generic class hierarchy, able to access:
- Any OleDB providers (including latest version of MSSQL);
- Oracle via direct access to the OCI layer;
- SQLite3, statically embedded to the executable (no external sqlite3.dll library).
The SynDBExplorer sample tool is now able to select a SQLite3 database as source.
Select "Sqlite3" as the database type when creating a new connection, and specify the full SQLite3 database as "Server name". Other properties (Database name, User ID, Password) are just ignored.
The SynDBExplorer is able to list all tables, and also column names and types - including indexes.
See http://synopse.info/fossil/finfo?name=SynDBSQLite3.pas
As you can see, adding such another Database to the SynDB classes model is just a very thin layer, calling the new SynSQLite3 unit.
Offline
Direct SynDBExplorer exe download link: http://synopse.info/files/SynDBExplorer.zip
Offline
And some nice enhancements of the tool:
http://blog.synopse.info/post/2012/01/1 … ect-export
One step in direction to more RDBMS integration with objects.
Offline