Robin: apology not specify in my previous mail that my koha version is 3.0.6, which has a preference variable to not use the zebra (NoZebra), so the search of bibliographic records are handled directly by MySQL, grateful by the response, I hope to clarify the problem, Greetings Ad ----- Mensaje original ----- Send Koha-devel mailing list submissions to koha-devel@lists.koha-community.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel or, via email, send a message with subject or body 'help' to koha-devel-request@lists.koha-community.org You can reach the person managing the list at koha-devel-owner@lists.koha-community.org When replying, please edit your Subject line so it is more specific than "Re: Contents of Koha-devel digest..." Today's Topics: 1. Re: Koha and DBIC (Marcel de Rooy) 2. Re: problem to perform a simple query (Robin Sheat) 3. VIAF and Koha 3.16.x (Partha Mukhopadhyay) ---------------------------------------------------------------------- Message: 1 Date: Mon, 15 Sep 2014 19:11:35 +0000 From: Marcel de Rooy <M.de.Rooy@rijksmuseum.nl> To: Koha Devel <koha-devel@lists.koha-community.org> Subject: Re: [Koha-devel] Koha and DBIC Message-ID: <809BE39CD64BFD4EB9036172EBCCFA31423D34C8@S-MAIL-1B.rijksmuseum.intra> Content-Type: text/plain; charset="iso-8859-1"

I am troubled by the idea that we should wrap all our dbic classes in yet more classes. Every example I've seen of this has more code by a factor of almost 10. I don't know if Koha is so complex that it requires a repository pattern. I think that it would require rewriting Koha. This changeover might just be too complex for us.

How much more difficult will this be for developers, and how much more overhead will it require if we wrap our objects in more objects? We'd have to fetch the Row objects, wrap them in KohaRow objects, wrap those in a KohaRowSet, and return them. Certainly, but far more complicated. I would say: Leave all storage related actions in Koha::Schema. KohaRow does not make sense to me. Furthermore, define the objects that actually have 'real' business logic and put that in some Koha::Object.

Marcel