Our ORM RESTful Framework is about to access any available database
engine.
It will probably change its name (since it won't use only SQlite3
as database), to become mORMot - could be an acronym for
"Manage Object Relational Mapping Over Tables", or whatever you may think
of...

We'll still rely on SQLite3 on the server, but a dedicated
mechanism will allow to access via OleDB any remote database, and mix
those tables content with the native ORM tables of the framework. A flexible
Virtual Tables and column mapping will allow any possible architecture: either
a new project in pure ORM, either a project relying on an existing database
with its own table layout.