First off, a note to Galen. I reported to you that I had experience with DBIx::Class. Make that Class::DBI instead. I am reading up on DBIx::Class now.
It seems that DBIx::Class grew out of Class::DBI and might be more sophisticated for our purposes. There is a perl monks comparison of these two here: http://www.perlmonks.org/?node_id=700283 with some pros and cons for each. What I like about Class::DBI is that it created a data model object for each table, i.e. something like Ourspace::Itemtype for the itemtype table. Instances of that object are loaded and initialised from the database. In the examples I have been reading kindly posted by Andrew Moore I am seeing field (attribute) accesses like the following using DBIx::Class ... $row->get_column('cn_source') This is not much different than the following: $hash->{cn_source} IMHO. Part of the advantage in an OR mapper is having first class data model objects, i.e. the above would become: $obj->cn_source and changing the value of the cn_source attribute is accomplished quite simply by $obj->cn_source('new_value') There might be some concern of the extra overhead involved in creating data objects for each database fetch. cheers rick -- ________________________________________________________________ Rick Welykochy || Praxis Services || Internet Driving Instructor When the power of love overcomes the love of power, the world will know peace. -- Jimi Hendrix _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
