We recently had a discussion about date/time support, but also other 
suggestions, which sooner or later end up at the point "cannot be done, would 
break backward compatibility". (See also: "Backward compatibility vs. new 
features (was: Re: dates, times and R)")

I'm always curious and monitoring trunk development, and now I have read in the 
draft release notes for 3.31:

> If an earlier version of SQLite attempts to read a database file that 
> contains a generated column in its schema, then that earlier version will 
> perceive the generated column syntax as an error and will report that the 
> database schema is corrupt.

...which leads me to some confusion. So there actually *are* features breaking 
compability? Wouldn't that be a chance for full date/time support as well?

_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Reply via email to