On 02/12/09 21:13, Rick Welykochy wrote: > Joe Atzberger wrote: > >> Chris' work is encouraging. ORM classes are definitely a different way >> of thinking about data though. The mapping is its own little ecosystem, >> and will require the structure to be maintained and updated (much like >> kohastructure.sql and updatedatabase). One great thing though, is that >> it combines with caching very naturally (caching an object, not just a >> DB row). > > Perhaps a move towards Koha objects in perl could accompany this change, i.e. > data model objects that present Koha constructs like Patron, Catalogue, Item, > etc. I think this is a way we need to go, and hopefully it will make it easier for people to contribute new features in future. At the moment some of the routines in the libraries are huge and full of side effects for the unwary. > > Having used an ORM before, I think it is important to monitor the performance > of the auto generated SQL, keep some metrics and optimise once the concepts > are functioning. It's very important, I've been down that road as well.
Cheers Colin -- Colin Campbell Chief Software Engineer, PTFS Europe Limited Content Management and Library Solutions +44 (0) 208 366 1295 (phone) +44 (0) 7759 633626 (mobile) colin.campb...@ptfs-europe.com skype: colin_campbell2 http://www.ptfs-europe.com _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
