The jackcess API is already fairly database-like. it has a Cursor API which enables index based lookups. It has row insert/update/delete. There is no support for transactions, so basically everything is auto-commit. a given db file must also be accessed in a single-threaded manner.
So, as i see it, there are 2 separate pieces of code being written. some "backend-api" for hsqldb...
Can you expand a bit on your first sentence? It sounds very intriguing, but i'm not sure what you mean.
The project would be a completely new project, separate from jackcess, so that project's license and any changes made to hsqldb would be completely up to your/my decision (this work is not tied to any company on my end).
In my spare time i run jackcess project. many, many people want to run jdbc on top of an access database file. i've been trying to find another open source project to do the sql heavy lifting, on to which i could bolt the backend interaction with an access database using jackcess.
the hsqldb sql parser seems to be pretty powerful and flexible. i was wondering if one of the developers could weigh in on the feasibility of using the sql parser for a different database backend. is it separable in some reasonable fashion such that it could be "relatively" easily used as a front end to a different "database" backend?.