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.
--Keith
This isn't specific to PHP, but ...
I am building a translation layer right now, in Perl.
You should be able to, using my library, easily convert SQLite2 databases to SQLite3, or the other way, or between SQLite and various other database products, within the next 2-3 weeks. The library does the standard "scan and write" approach, analagous to a "dump and restore" but not so crude (it translates and emulates SQL too).
Go to http://search.cpan.org/ ; look up 'Rosetta' and 'SQL::Routine'. They are pre-alpha, but I should have the functionality you need within 3 more releases of each.
My library is also being ported to Parrot asap, so that all the languages which have compilers targeting Parrot (I think someone's even doing PHP) can use it.
-- Darren Duncan
