https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30490
--- Comment #8 from Marcel de Rooy <[email protected]> --- (In reply to Katrin Fischer from comment #7) > (In reply to Marcel de Rooy from comment #3) > > (In reply to Marcel de Rooy from comment #2) > > > (In reply to Katrin Fischer from comment #1) > > > > My feeling would be that if you delete a parent itemtype, it should set > > > > the > > > > field to NULL in the 'child itemtypes'. Does that make sense? > > > > > > Yes. That is the same as RESTRICT. > > > > Actually no :) You describe SET NULL but I opt for RESTRICT. You cannot > > delete the parent type if there still is a child itemtype. > > Hm, I not sure about this one. > > You might just add a parent itemtype for testing, the only purpose right now > is the max checkouts, later decide to remove it... It's not a > required/mandatory field, so I'd day NULL would be ok, maybe with a > confirmation warning in the GUI. > > This way you need to remove it in all itemtypes first, more clicks, but I > can live it, just think the other is nicer :) This would be an enhancment actually. Now I restore the sync gap between dbrev and structure. You are invited to open a new report? :) -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
