Hi, On Thu, Nov 13, 2008 at 3:06 AM, Rick Welykochy <rick@praxis.com.au> wrote:
Paul POULAIN wrote:
one thing that is a real shame is that, atm, if something fails due to FK constraint, the user is NOT warned that something was wrong. he just sees that the data has not be saved. That's really bad !
The INNODB driver for MySQL reports an error if the FK doesn't exist at creation time.
If by "user" you mean the database client, then yes, there is an error message:
ERROR 1452 (23000): Cannot add or update a child row: a foreign key constraint fails
If by "user" you are referring to the librarian or Koha user, then it is up to the Koha application to intercept and process the above error if it does happen and take remedial action, i.e. send an indignant email to Koha-dev!
I think the point is that by and large, Koha doesn't intercept FK violation errors and do something sensible with them. This needs to be improved, though I must admit that I smiled at the image of having such errors automatically forwarded to koha-devel. Regards, Galen -- Galen Charlton VP, Research & Development, LibLime galen.charlton@liblime.com p: 1-888-564-2457 x709 skype: gmcharlt