Hi,
h2 1.3.175 -> 1.3.176 renames org.h2.constant.SysProperties to
org.h2.engine.SysProperties, this breaks applications/libraries which
depend on the public classes being stable.
(e.g. GridGain)
Is this intentional?
I think its best for a patch release to use the same API structure, for
rena
How do you plan to prevent such references in the future? Will you
validate CHECK constraints at creation time somehow or are you saying
you're going to disallow CHECK to reference external tables at all? I
hope it's not the latter because I've used it to enforce some
interesting use-cases. For
On 04/07/2014 3:12 AM, Noel Grandin wrote:
On 2014-07-04 08:51 AM, cowwoc wrote:
How is this even possible? When I try creating foreign keys to tables
that are only created later,the CREATE TABLE
statement fails ("table X does not exist"). Can you provide an
example of problematic code?
Hi,
To re-create the database, you can use the "Recover" tool.
Regards,
Thomas
On Sun, Jun 29, 2014 at 11:38 PM, Ravindra Gullapalli <
sharewithra...@gmail.com> wrote:
> Another input (might be useful)
>
> I did a checkout of source code of revision # 5751 and tried to generate
> script. Howe
Hi,
To find the changed source code, you can go to
https://code.google.com/p/h2database/source/list . This case is
https://code.google.com/p/h2database/source/detail?r=5707 - test case is
here:
https://code.google.com/p/h2database/source/diff?spec=svn5707&r=5707&format=side&path=/trunk/h2/src/test
On 2014-07-04 08:51 AM, cowwoc wrote:
How is this even possible? When I try creating foreign keys to tables that are
only created later,the CREATE TABLE
statement fails ("table X does not exist"). Can you provide an example of
problematic code?
We allow general SQL statements in our CHECK
