I agree. I'd rather use DBIC directly and extend what we already have. It's just an idea if the conclusion is we can't do that. Kyle http://www.kylehall.info ByWater Solutions ( http://bywatersolutions.com ) Meadville Public Library ( http://www.meadvillelibrary.org ) Crawford County Federated Library System ( http://www.ccfls.org ) Mill Run Technology Solutions ( http://millruntech.com ) On Wed, Sep 17, 2014 at 6:49 AM, Colin Campbell < colin.campbell@ptfs-europe.com> wrote:
A Koha::Object sounds like extremely poor design. What kind of object is a Koha::Object, what are its properties, when we say a Koha::Biblio isa Koha::Object what does that mean? In practice what meaningful properties it has it inherits from Koha::Schema::Result::Biblio which is liable to be a better representation than the vaguer Onject.
In practice I've recently written some scripts which in first version used some abstractions built around dbic ResultSets, As I added to them I stripped out out the abstractions and used the dbic result sets as I found this generated cleaner, more straightforward code.
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) 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/