CREATE TABLE test1(a int default serial, primary key(a)) // CREATE TABLE test2(a int default serial, b int, c int, primary key(a), foreign key b(b) references test1(a) on delete set null, foreign key c(c) references test1(a) on delete set null)
I don't see, why those statement should be rejected with
General error;-7040 POS(1) Referential constraint not allowed. CREATE TABLE test2(a int default serial, b int, c int, primary key(a), foreign key b(b) references test1(a) on delete set null, foreign key c(c) references test1(a) on delete set null)
Multiple referencial constraints to one table should be allowed!
I'd like to get a comment in this one! Either say "it isn't a bug, and it won't be supported", or let me know when it might be supported.
If this is bad design, tell me a better design. Here's the problem i'd like to solve: I have a table with items in it, and each item get's two user-IDs: the user-ID of the user that created the item and the user-ID of the user that last changed the item. There is a table with all user-IDs in the system, and so i'd like to but a foreign-key on the two user-ID columns. There's nothing special about that, and that is possible with any major DBMS i know, except MaxDB of course.
-- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
