Hi Lukas,
Further information
In H2 version 1.3.170 -
* Fix for a bug where we would sometimes use the wrong unique
constraint to validate foreign key constraints.
I just checked and my database was built with version 1.3.166, although
I upgraded to 1.3.170 some time ago, the bug must have already been in
the database.
That is why running the script to / runscript fixed it.
Thanks for your help and I'm sorry for using up your time when JOOQ was
doing it's job perfectly!
Thanks, Ryan
On 20/02/2013 10:47 PM, Lukas Eder wrote:
> The schema for the SALES_LEAD_INTERESTED_OTHER table is
>
> CREATE TABLE SALES_LEAD_INTERESTED_OTHER(
> SALES_LEAD_INTERESTED_OTHER_ID LONG IDENTITY,
> SALES_LEAD_ID LONG NOT NULL REFERENCES SALES_LEAD,
> INTERESTED_IN VARCHAR(1000),
> INTERESTED LONG NULL REFERENCES VALUE_LIST_ITEM,
> PLAN_ID LONG NULL REFERENCES PLAN
> )
Would changing the DDL to this change anything? I'll also try your
syntax on my side.
In fact, could you provide me with the DDL for PLAN and SALES_LEAD as
well, please? Including all constraints. I can't seem reproduce this,
otherwise...
--
You received this message because you are subscribed to the Google
Groups "jOOQ User Group" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "jOOQ User
Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
