Oh, this is nice (not having to worry). I assume that by "The database file format is fixed", you mean "fixed until SQLite4 is around", at which point the updating of files will also be required.
Is this correct (or should i be getting some sleep)? Regards On Jul 23, 2011, at 8:29 PM, Richard Hipp wrote: > On Sat, Jul 23, 2011 at 12:53 PM, Panos Katergiathis > <eyeproto...@gmail.com>wrote: > >> Hello all >> >> I fail to understand what "Upgrading from version x.x.x.x to x.x.x.x" >> means. >> >> If i have understood properly so far, SQLite databases are single files, >> that are structured according to some specification, which - of course - >> will evolve in the future. So, those files will need to be updated in order >> to conform to the new specification when available. >> > > No. > > The database file format is fixed. You do not need to update your database > files. > > "Upgrading from version xxxxx to yyyyy" means that you should use version > yyyyy of the SQLite software in the applications you write, usually because > it is faster or it fixes some obscure bug. If you are not the person who > compiles SQLite into applications, then you shouldn't need to worry about > this. > > > >> >> However, the current PHP version (on the current Debian stable release) >> supports SQLite version 3.7.3, so what would updating mean? Should one use >> more recent php versions, that would certainly be able to read/write new >> SQLite files, and would that process automatically update the internal >> structure of files that were created with the older PHP version? >> >> Or, would one use some other tool (what would that be?) to update any >> SQLite files, and then would these files still be writable/readable from the >> older PHP version? >> >> If files (and file versions) are not backward compatible, how would one >> proceed in selecting a language (and a language version) so as to not get in >> trouble? For example, how can one know what SQLite version the current >> JavaSE release supports? >> >> I would be thankful if you could shed some light and help me overcome this >> confusion, or point me to the right direction. >> >> Regards >> _______________________________________________ >> sqlite-users mailing list >> sqlite-users@sqlite.org >> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users >> > > > > -- > D. Richard Hipp > d...@sqlite.org > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
