-----Original Message----- From: koha-devel-bounces@lists.koha-community.org [mailto:koha-devel- bounces@lists.koha-community.org] On Behalf Of Galen Charlton Sent: Wednesday, 20 April 2016 12:03 PM To: Tajoli Zeno <z.tajoli@cineca.it> Cc: koha-devel <koha-devel@lists.koha-community.org> Subject: Re: [Koha-devel] Frameworks / DB constraints
Hi,
On Tue, Apr 19, 2016 at 11:16 AM, Tajoli Zeno <z.tajoli@cineca.it> wrote:
I'm agree on solution proposed by Jesse: creating the foreign key with ON DELETE SET NULL.
At the moment, biblio.frameworkcode doesn't permit NULL values, and InnoDB doesn't support ON DELETE SET DEFAULT. That doesn't mean that we couldn't do more work so that frameworkcode IS NULL is fully supported, but it's not *just* a matter of adding the FK.
I'm more in favor of either:
- adding a FK that does ON DELETE RESTRICT. For most databases, this would require adding a row to biblio_framework whose frameworkcode is the empty string. - having the business logic take care of falling back to the default
I agree with Galen. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Office: 02 9212 0899 Direct: 02 8005 0595 framework
when necessary.
Regards,
Galen -- Galen Charlton Infrastructure and Added Services Manager Equinox Software, Inc. / Open Your Library email: gmc@esilibrary.com direct: +1 770-709-5581 cell: +1 404-984-4366 skype: gmcharlt web: http://www.esilibrary.com/ Supporting Koha and Evergreen: http://koha-community.org & http://evergreen-ils.org _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha- community.org/ bugs : http://bugs.koha-community.org/