Out of curiosity, how hard would it be to build a translation layer? I
suppose it's easier to keep both versions around, and upgrade when
necessary, but as a technical problem, it's at least interesting? Only
downwardly, of course, so there would be no expectation that 2.X could use
3.X, just the reverse. It had sounded as if only the file format was the
problem; is it more than that?
I'm not pushing, in any sense, just wondering if anyone has looked at this issue with an eye to resolving it.
The PHP library IS the translation layer.
The crux of the issue is that the formats are NOT compatible, nor are the API's. What Dr. Hipp suggested is the best possible course. Link with both API's which _DO_ have separate naming conventions making it possible to support both formats concurrently. All new databases follow Sqlite3, legacy follow Sqlite2.
There are signatures in the database files to distinguish between the two. Use the tools that are available to add the layer of abstraction necessary. Don't force that on SQlite itself.
Its all summed up in one sentence, which is the first one that appears at sqlite.org:
"SQLite is a small C library that implements a self-contained, embeddable, zero-configuration SQL database engine."
The focus is there, anything beyond that is up to the implementation.
-- Craig Morrison =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= http://www.mtsprofessional.com/ A Win32 email server that works for You.
