Thanks,
I just ran a SCRIPT TO and RUNSCRIPT on the database, still using H2
170, and the issue appear to have corrected itself, so that doesn't give
a reproducable a test case. I'll try and keep a look out for it and
narrow it down.
On a side note, is it possible for the Constraints in the Information
Schema table to change after they have been created?. I ask because I am
working on a version of the database which was taken as a copy of the
production database (A straight file copy, not using SCRIPT TO or
anything). In the production database the constraint is correct, but in
my copy it is incorrect.
Thanks, Ryan
On 29/04/2013 7:54 PM, Noel Grandin wrote:
Hmm, looks like a bug.
If you can provide a reduced test case, I can take a look at fixing it.
On 2013-04-29 04:54, Ryan How wrote:
Hi,
I came across this bug in version 169 causing issues (Well I think it
is this bug, I'll explain below). I updated to 170, and rebuilt the
database and it seemed to be fixed (This was a few months ago)
However, I seem to be getting this issue again.
If you see the table below, The Foreign key relationship from
Quotation_Plan to Quotation (Last one in the table) appears to be
referencing a unique constraint rather than the primary key. I was
getting this behaviour a lot in 169, but it doesn't seem that 170 has
fixed it completely.
Am I interpreting the information below correctly? Are there any more
details I can provide?
The exact issue this is causing for me is that JOOQ is generating
code incorrectly because it cannot get the (correct?) information
about relationships.
--
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
