Begin forwarded message:
> From: Marien Zwart <m_zw...@123mail.org> > Date: November 12, 2009 1:26:11 PM EST > To: sqlite-users-ow...@sqlite.org > Subject: failing attempts at sending "Feature request: PRAGMA > maximum_file_format" > > Hi, > > I'm really sorry to bother you, but I've now attempted to send the > following to the list twice and apparently it is eaten somewhere (some > spam filter?). This was about a week ago now, so I'm assuming the mail > isn't simply waiting in the moderation queue (it should not be > ending up > there anyway, because I'm subscribed and receiving mail from the list > just fine). There is probably something wrong with my mail setup, > but I > cannot figure out what. If you could have a look at this message's > headers or whatever logs the mailing list software keeps that would be > very much appreciated. > > This was the text from the message I'm trying to send: > > SQLite currently supports two slightly different ways of setting the > file format used for new databases: PRAGMA legacy_file_format at run > time and defining SQLITE_DEFAULT_FILE_FORMAT at compile time. The > latter > lets you set the default format created to any of the supported > formats > (currently just 1 or 4, according to the documentation). The former > lets > you pick either the most compatible or the most recent format (so > currently also 1 or 4). > > To write more future-proof code I would like to have something like > PRAGMA default_file_format or PRAGMA maximum_file_format that lets me > explicitly specify the highest file format version SQLite will use for > new databases. > > My reasoning is that while with versions of SQLite that currently > exist > I can accept PRAGMA legacy_file_format=0 (I can safely assume SQLite > 3.3 > or higher is available) if my code gets used with some future > version of > SQLite that introduces a new file format I will start creating > databases > that are not backwards compatible without warning. So I would like > to be > able to use something like PRAGMA default_file_format=4 instead, which > would cause this future version of SQLite to create databases that can > be read by SQLite 3.3 and up. (I am not sure what to do when the > requested default_file_format is higher than the highest supported > version. It may be reasonable to handle this as equivalent to PRAGMA > legacy_file_format=0 instead of treating it as an error.) > > Does this sound like something worth adding? If it does I could try to > cook up a patch, although I would probably need some pointers for > that, > not being familiar with the SQLite code. > > Thanks in advance! > > -- > Marien. D. Richard Hipp d...@hwaci.com _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
