Subject | How to handle foreign key constraint violations elegantly? |
---|---|
Author | mitch_landor |
Post date | 2008-04-14T16:53:46Z |
Is there a way to elegantly present this error to users?
Can I pass a Firebird foreign key constraint violation message &
message ID to Delphi so that I can check that it is indeed a foreign
key constraint violation?
Is there a way to pass the particular table names involved and then
give the user a message explaining the problem? Would it be better to
make an exception & exception message in the DB for each table?
How does one normally do this? Can it be done by one generic message
or procedure?
Thanks
Mitch
Can I pass a Firebird foreign key constraint violation message &
message ID to Delphi so that I can check that it is indeed a foreign
key constraint violation?
Is there a way to pass the particular table names involved and then
give the user a message explaining the problem? Would it be better to
make an exception & exception message in the DB for each table?
How does one normally do this? Can it be done by one generic message
or procedure?
Thanks
Mitch