2013/6/18 Noel Grandin noelgran...@gmail.com
On 2013-06-09 13:43, Lukas Eder wrote:
Is this the intended behaviour? In my opinion, both constraints should
appear in the constraints view, though. Note, this is how I would query for
CHECK constraints in the SQL standard INFORMATION_SCHEMA
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
2013/6/19 Noel Grandin noelgran...@gmail.com
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
Hello,
Here's a simple script creating a table with two CHECK constraints:
*create table* x (
a int *check *(a 0),
b int,
*constraint *x_c *check *(a b)
);
The first check constraint is scoped to a single column, whereas the
second one is scoped to the whole table.
When trying to
