On Tue, Sep 11, 2001 at 04:14:55PM +1000, Robert McArthur wrote: > Following on from the Class::DBI, is anyone using SPOPS inside/with > TT? I know there's OpenInteract (hi Chris!), but SPOPS seems to be > Class::DBI with a some (significant) extras. Or am I just confused :-)
I've had a brief look at SPOPS but don't really know it ... As the new maintainer of Class::DBI, I'm obviously open to suggestions, but I'm coming more and more to view Class::DBI not so much as a way of serialising objects to a database, but to easily represent a database in objects. Slightly nit-picky perhaps, but I think it's an important distinction. Many of the other 'persistence' models seem to be more for people who don't want to have to think about database design and query optimisation and complex relationships etc, but who want to store their objects' data somewhere, and don't have an OORDBMS to hand, just a 'normal' one. Class::DBI, OTOH, really starts to come in to its own when you already have a database, and want to avoid having to write all the normal repetitive code that comes with writing classes to go with that. The recent work on relationships (we now have hasa, and has_list, which, whilst needing lots of good examples in the docs, now make it easy to handle both one to many and many to many joins, with cascading deletes where appropriate), is highlighting this power even more than I would have expected, especially when coupled with something like TT. My current vision of Class::DBI is that it makes life easy for people who prefer to spend more of their time on database work than on Perl code... Of course, like all my opinions, I reserve the right to change this vision completely on a whim ;) Tony -- -------------------------------------------------------------------------- Tony Bowden | [EMAIL PROTECTED] | http://www.tmtm.com/ all history is too small for even me; for me and you,exceedingly too small --------------------------------------------------------------------------
