Pablo, you might as well import using the web tool, which handles deletion too.
On Tue, Jun 24, 2014 at 4:38 PM, Pablo Bianchi <[email protected]> wrote: > Hi Robin, > > I'm aware about turning foreign keys constrains off is risky, what I was > trying to know is how risky could be, but OK, I realize that depends of > each database, and always a bad idea. > > So at least we can say manual (and also bulkmarkimport.pl -d option) > should > be updated (MySQL >~5.5)* adding a note about DELETE FROM biblio way not > always will work right away. This bring us to: > > > In some cases the constraints will propagate the delete, > > in other cases they won't. These differences are by design. > There are good design reasons for no letting "delete biblio" table > propagate in all/any cases? Propagation in any case will make really simple > to update manual and bulkmarkimport. > > *I'll then fill a bug report about this two issues (manual and > bulkmarkimport -d option) update. > > Regards, > Pablo > > _______________________________________________ > Koha mailing list http://koha-community.org > [email protected] > http://lists.katipo.co.nz/mailman/listinfo/koha > -- Tomás Cohen Arazi Prosecretaría de Informática Universidad Nacional de Córdoba ✆ +54 351 5353750 ext 13168 GPG: B76C 6E7C 2D80 551A C765 E225 0A27 2EA1 B2F3 C15F _______________________________________________ Koha mailing list http://koha-community.org [email protected] http://lists.katipo.co.nz/mailman/listinfo/koha
