I completely agree. You've described the issue more succinctly and eloquently than I have by far.
Kyle On Thu, Sep 11, 2014 at 4:15 AM, Colin Campbell < [email protected]> wrote: > Its worth keeping in mind that DBIC is an Object Relational mapper and > that as such returns objects which are often better abstrations than > those currently embodied in Koha's module approach which tend to fiddle > with the representation of the entity not always very consistently. In a > multitude of cases a ResultSet of x objects and their inherent getters > and setters is all we need to construct the operations we need. In such > cases wrapping the layer in another one for purely formal reasons > contributes little except for more space to harbour bugs. > DBIC allows you to add extra methods to these objects and I'm sure in > time we'll identify plenty of these but we should be very thorough in > reviewing whether we need them, how we've implemented them and whether > the need is merely pointing up a shortcoming in the schema. > > Colin > > -- > Colin Campbell > Chief Software Engineer, > PTFS Europe Limited > Content Management and Library Solutions > +44 (0) 800 756 6803 (phone) > +44 (0) 7759 633626 (mobile) > [email protected] > skype: colin_campbell2 > > http://www.ptfs-europe.com > _______________________________________________ > Koha-devel mailing list > [email protected] > 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 [email protected] 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/
