Subject | Re: Foreign key constraint violation |
---|---|
Author | hfsnell |
Post date | 2008-02-28T03:13:24Z |
Thank you for make my DDL brevitier!
My db have crashed many times! But one time it crashed by this foreign
key constraint and another time it crashed by another foreign key
constraint.
inactive. But I always check after importing, the db is at good status.
> Now, as I understand, you have ended up with several records inYes, it is correct!
> OBJECT_BAL without a parent record in OBJECT_LIST, thus violating
> FK_OBJECT_BAL_1. Is this correct?
My db have crashed many times! But one time it crashed by this foreign
key constraint and another time it crashed by another foreign key
constraint.
> I'm hoping one of the experts will join in, but in the meantime I haveis it
> one question for you: Is FK_OBJECT_BAL_1 always present/active? Or
> perhaps temporarily removed at certain operations?When I import data from outside (such as xls file) this contraint is
inactive. But I always check after importing, the db is at good status.