On 2013-06-19 08:23, Lukas Eder wrote:
Are there any plans to move towards semantic versioning
(http://semver.org) with H2? The current versioning scheme doesn't
formally allow to remove such backwards-compatibility flags again.
With semantic versioning, I think it would be OK to change the default
behaviour of the INFORMATION_SCHEMA.CONSTRAINTS table in a minor
release...
In general, being a database engine means having to be a lot more
careful about changing default behaviour than other software components,
so no, I don't think we're going to be making a habit of doing it
frequently.
Our general plan is that when we get the new MVStore engine
production-ready, we will
- bump the major version to 1.4
- default all of the configuration settings to the "new" setting
- remove all of the backwards compatibility flags
So you have anything new that you'd like to be the default in the next
major version, you should be busy creating a patch now, with it's
behaviour hidden behind a flag :-)
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/h2-database.
For more options, visit https://groups.google.com/groups/opt_out.