I am developing with ultralite 12 with build 3873, recently I found a problem that foreign key MUST be defined in the order which each column is defined in the "referenced to " table. otherwise it will give me an error.
For example: I have two table
In test1 we have value
Then if I have a reference constraint defined as following
it works fine. i can do the insert
However, if I define the constraint as following
When I try same insert it gives me an error. Note that the only change is the foreign key order in both
What is worse is that when I convert my sybase anywhere12 database to ultralite, the foreign key constraint is created based on current table's column id, which may lead to the issue I was talking about.
asked 07 Jun '13, 23:34
This appears to be a bug. I have opened CR #741393 to investigate this issue further.
Notably, the reverse order on the insert does work, but would be incorrect:
insert into test2 ("fk1", "fk2", "pk3") values(2,1,0);
I will update this thread when we have additional information available.
answered 11 Jun '13, 09:18