hello thomas,
> This indeed is a bug. I have been able to reproduce the error with the > provided information. The problem is that you created exactly 30 foreign > keys. As a workaround you can drop the 'last' foreign key first. Last means > the last foreign stored in the catalog, i.e. the last foreign key returned > from > > SELECT FKEYNAME FROM DOMAIN.FOREIGNKEYS WHERE TABLENAME = 'EVENT_BRIEF' which is probably what happens internally when I fetch all foreign keys via the jdbc metadata interface? just to confirm your assessment I modified our tool to remove foreign keys in reverse order as a temporary workaround and it works now. > > Afterwards it should be possible to drop the other foreign keys in any > arbitrary order. > The bug fix is easy and will be available with the next SAPDB version. > > Thomas any rough idea when the next maintenance release is scheduled? thank you very much for once again proving that sapdb is probably the best-supported oss database. best regards, robert _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
