I guess I have the same attitude as an old Main Framer I tried to sell a Datapoint Arc Net long, long ago. His summation of the presentation was, " I have enough damn trouble with one CPU. Why would I want a whole network full of them!" I can barely keep one release of a database running, why would I want two! :-)
I have yet to have worked with any database engine that I could not migrate to a new release external to any code I have written. Including Paradox and XBase if those qualify as engines. To each his own. Fred > -----Original Message----- > From: Igor Tandetnik [mailto:[EMAIL PROTECTED] > Sent: Thursday, November 03, 2005 12:01 PM > To: SQLite > Subject: [sqlite] Re: Request for comment: Proposed SQLite API changes > > > Fred Williams wrote: > > Thanks. I guess I never considered using two different releases of > > any product within the same executable. Wonder how many use this > > feature and why? > > SQLite2 and SQLite3 have incompatible database formats. > Neither can read > the databases produced by the other. One might want to write a > conversion utility that reads data with sqlite2_* API and > writes it to a > new database with sqlite3_*. Or say you cannot migrate your > legacy data > for some reason so you need your software to be able to work > with both > formats. > > Igor Tandetnik >
