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. 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. cheers rickw -- _________________________________ Rick Welykochy || Praxis Services Prohibition was better better than no liquor at all. -- Kin Hubbard