> Why not remove the feature but create a seperate utility project that > converts any version of SQLITE DB to the latest version.
i think it's better to let it in. why save a few bytes for removing such important functionality. by the way, same for md5, you should add support. imho there is no reason at all to exclude functionality in default environment. rene ----- Original Message ----- From: "Allan Edwards" <[EMAIL PROTECTED]> To: "'Greg Obleshchuk'" <[EMAIL PROTECTED]>; "'D. Richard Hipp'" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Saturday, February 07, 2004 12:41 AM Subject: RE: [sqlite] OK to drop support for legacy file formats? > Now there is experience talking. I agree with this view point. > > -----Original Message----- > From: Greg Obleshchuk [mailto:[EMAIL PROTECTED] > Sent: Friday, February 06, 2004 4:18 PM > To: D. Richard Hipp; [EMAIL PROTECTED] > Subject: Re: [sqlite] OK to drop support for legacy file formats? > > Hello, > Why not remove the feature but create a seperate utility project that > converts any version of SQLITE DB to the latest version. > > In this way SQLite can be just what it is small and fast. There would be a > tool from the orginal source which you would know would work and simple to > use. > > The current version of SQLite would need to error when openning an older > formatted DB file. > > regards > Greg > > > > ----- Original Message ----- > From: "D. Richard Hipp" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Saturday, February 07, 2004 1:05 AM > Subject: [sqlite] OK to drop support for legacy file formats? > > > > If you use a modern version of SQLite (version 2.6.0 through 2.8.11) > > to open an older database file (version 2.1.0 through 2.5.6) the > > library will automatically rebuild all the indices in the database > > in order to correct a design flaw in the older database files. > > > > I am proposing to drop support for this auto-update feature. > > Beginning with 2.8.12, if you attempt to open a database file > > built using version 2.5.6 or earlier, the open attempt will > > fail (with an appropriate error message). You will have to > > update the database file manually. > > > > Would this proposed change cause anyone unreasonable hardship? > > -- > > D. Richard Hipp -- [EMAIL PROTECTED] -- 704.948.4565 > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
