https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20271
--- Comment #262 from David Cook <[email protected]> --- (In reply to Nick Clemens from comment #261) > Maybe it is too late to ask this question: Rather than joining items and > deleteditems, can we join them into a new table and provide views for both > of the old tables? This would prevent breaking reports across the board. > > biblio, deletedbiblios => biblios? > items,deleteditems => all_items? > > This is going to be a big problem for existing users, it is going to be many > reports, and it is going to cause disruption. Havign views that keep the > reports working would be a huge boon. It's an interesting idea. It would be nice to preserve that backwards compatibility. I think MySQL supports read/write for views, so in theory it could work... -- I imagine another issue would be changing the tables used in the DBIC definitions? However, I don't think Biblio or Item were extensively used directly... C4/Circulation.pm: my @itemnumbers = $schema->resultset('Item')->search( circ/renew.pl: $item = $schema->resultset("Item")->single( { barcode => $barcode } ); Koha/Edifact/Order.pm: my $i_obj = $schema->resultset('Item')->find( $item->itemnumber ); Koha/EDI.pm: my $item = $schema->resultset('Item')->find( $ilink->itemnumber ); Koha/EDI.pm: my $rs = $schema->resultset('Item')->search( Koha/EDI.pm: my $item = $schema->resultset('Item')->find( $ilink->itemnumber ); Koha/BiblioUtils.pm: $schema->resultset('Biblio')->search( So then it would just be updating Koha/Item.pm and Koha/Biblio.pm with the new ResultSet module name. -- 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/
