If we set items.itype to NULL, aren’t we potentially causing problems for people who want to JOIN “statistics” and “items” tables?
Do we already have software logic to prevent Item Types from being deleted if they’re used in items or biblioitems? David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 From: koha-devel-boun...@lists.koha-community.org <koha-devel-boun...@lists.koha-community.org> On Behalf Of Tomas Cohen Arazi Sent: Wednesday, 31 July 2019 5:08 AM To: Katrin Fischer <katrin.fischer...@web.de> Cc: koha-devel <koha-devel@lists.koha-community.org> Subject: Re: [Koha-devel] items.itype FK constraint? We can set a FK constraint while allowing NULL too. The reason for me to post this on the list is to hear (probably) historical reasons for this constraint not to be set already at DB level. Thanks for your replies! El mar., 30 jul. 2019 a las 16:05, Katrin Fischer (<katrin.fischer...@web.de <mailto:katrin.fischer...@web.de> >) escribió: Hi Sophie, I think on database level we need to allow NULL, because of the item-level_itype 'record level' setting. I understand that itemtypes are not set on item level at all in that case? Katrin On 30.07.19 16:32, Sophie Meynieux wrote: Hello, But itype must not be null if syspref item-level_itype is on, isn't it ? S. Meynieux -- Responsable support BibLibre + 33 (0)4 91 81 35 08 http://www.biblibre.com Le 29/07/2019 à 20:17, Katrin Fischer a écrit : +1 With a on delete set null? On 29.07.19 19:39, Tomas Cohen Arazi wrote: Why shouldn't we add it :-D -- Tomás Cohen Arazi Theke Solutions (http://theke.io <http://theke.io/> ) ✆ +54 9351 3513384 GPG: B2F3C15F _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org <mailto: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/ _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org <mailto: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/ _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org <mailto: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/ _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org <mailto: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/ -- Tomás Cohen Arazi Theke Solutions (http://theke.io <http://theke.io/> ) ✆ +54 9351 3513384 GPG: B2F3C15F
signature.asc
Description: PGP signature
_______________________________________________ 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/
