Yes, although not a very common case, in yours looks 100% justified. Maybe you did hit a MaxDB limitiation or a bug. Let's wait to see what SAP people have to say about it. Did you try with another type of on-delete-action instead of set null?
Regards & hapy new year, Martin Cordova -- Dinamica - RADical J2EE framework open source, easy and powerful http://www.martincordova.com On 1/2/06, Sven Köhler <[EMAIL PROTECTED]> wrote: > > I don't think it is because of the number of FKs, I have tables with 2 > > FKs on MaxDB 7.6. I suspect the cause is the fact that both FKs refer > > to the same table. > > Oh, you're possibly right. My 2 FKs were also referencing the same > table. But that should still be possible, don't you think? > > > > -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
