Personally I think DBIx::Class is the biggest load of crock out there.
It's much slower, awkward to use, time consuming to learn, and as soon
as you try to do some complicated queries you'll end up dropping it
anyway. ORMs simply cannot work in the long run:-
http://www.codinghorror.com/blog/2006/06/object-relational-mapping-is-the-vietnam-of-computer-science.html
I found SQL::DB recently, which looks interesting to me, but haven't had
chance to work with it yet. It might be what you are looking for.
Lyle
John Karr wrote:
I'm still learning Catalyst and find that I don't like DBIx. As a counter
example I love Template Toolkit, for exactly the same reason I hate DBIx.
With TT html is in html, while DBIx seperates the database from SQL, if I
were capable of writing an ORM (which I am not) it would be much more like
Template Toolkit. Also I'm primarily a sysadmin working on some volunteer
programming projects while out of work, so even though it might well be
worth coming to terms with DBIx if I did more development, crawling through
DBI seems a more efficient way for me to get working code written.
The alternatives I've been able to discover are DBI and RoseDB. Is there any
case (given why I've already stated I dislike DBIx) for RoseDB, and are
there any other alternatives that work well with Catalyst that I have not
found?
_______________________________________________
List: [email protected]
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/[email protected]/
Dev site: http://dev.catalyst.perl.org/
_______________________________________________
List: [email protected]
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/[email protected]/
Dev site: http://dev.catalyst.perl.org/
