What if instead of refusing to open the database at all, it opened the database read-only. Would opening older databases read-only mitigate any hardships that refusing to open older databases might cause?
My 2 cents, that sounds like the most user friendly approach, that way if a user has an old format database BUT for some inexplicable reason they only have the newer version of sqlite; they could at least use the sqlite terminal monitor to ".dump" it and re-create it via the usual:
sqlite old.db .dump | sqlite new.db
This approach is extremely unfriendly to embedded environments where the sqlite executable is not available. I want to place my vote for keeping the upgrade conversion routines, but as a compromise allow people to build without the routines using the SQLITE_OMIT_FEATURE idiom. Without the ability to upgrade on the fly we would need to write our own utility to do the same thing anyway.
Thanks, Ben
--
"Still my pen bleeds and stains the paper with thought."
- Illogic, "One Brick"--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
