On 18 September 2014 1:49:34 am NZST, Colin Campbell <colin.campbell@ptfs-europe.com> wrote:
Greetings,
Just to add to the confusion ;) When I wrote "some Koha::Object" here, I was not literally suggesting Koha::Object, I was thinking of something like Koha::Biblio or Koha::Patron etc. That’s what I understood. So physically, we may have the tables we currently have accessed via DBIC, but the Koha::Biblio object would blend DBIC objects related to Biblios and Items. Right? This would mean
On Wed, Sep 17, 2014 at 08:50:37AM -0400, Mark Tompsett wrote: that Koha::Biblio would provide whatever methods regardless of the backend structure.
Trouble is it sidesteps fixing the schema. The interplay between biblio and biblioitems will remain a problem for maintenance in future. There is already special code added to link the classes because their relationship is not maintained by the database. Special cases tend to grow over time and spawn more special cases.
It's not an either/or proposition, having Koha::Biblio doesn't mean you can't fix the schema too. It just means all the business logic for dealing with it is in that module/object. Instead of strewn about in scripts all over the place. Chris
C.
-- Colin Campbell Chief Software Engineer, PTFS Europe Limited Content Management and Library Solutions +44 (0) 800 756 6803 (phone) +44 (0) 7759 633626 (mobile) colin.campbell@ptfs-europe.com skype: colin_campbell2
http://www.ptfs-europe.com _______________________________________________ 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/
-- Sent from my Android device with K-9 Mail. Please excuse my brevity.