default to SQLite not HSQLDB in Base
I was going to refrain from comment but perhaps I'll begin with a few Pros & Cons:
Pros
- + Will result in a native SQLite 3.x driver for Base on all platforms
+ Eliminates Java dependencies from the back-end database engine
+ Might stabilize the "Embedded database" product due to code rework or proper unzip to disk during use
+ Might result in auto-configurations (pre-sets & checkbox options) for various engines (including HSQLDB 1.8.0 & 2.x for migration purposes)
+ If implemented as a separate, external, database file: offers direct database access from other applications
+ If implemented as a separate, external, database file: only 1 file in addition to the Base (.odb) front-end file
- - Significant step backwards from HSQLDB 2.x and even HSQLDB 1.8.0 in terms of SQL support and features
- No easy or realistic migration path from default single-user to client-server like we enjoy with HSQLDB
- May lack seamless support for legacy "Embedded databases"
- If implemented as a separate, external, database file (as it should be for stability and external .db access): now 2 files to distribute (.odb + .db)
- Missed opportunity to integrate H2 "mixed mode" for maximum flexibility including multi-user environments; also 2 files to distribute just like SQLite; also an Android candidate like SQLite (LibO is apparently targeting Android as a future goal)
