Re^2: Class::DBI -- does it get any easier?

Tangram is similar. However, things like that end up having limitations that become problems in real-world apps. With Class::DBI, there is literally no limit on what SQL you can use with it. That's the reason I use it.

Comment on Re^2: Class::DBI -- does it get any easier?

Replies are listed 'Best First'.
Re^3: Class::DBI -- does it get any easier? by Anonymous Monk on Nov 12, 2004 at 19:52 UTC
I can see it would be a problem when making larger apps and apps that use existing tables, definitely. But for building new apps, it is unbelievable useful. I have one real-world app running on our intranet right now, but it's pretty light use and doesn't have that many tables to it. The "Tables" link above seems fairly similar to ActiveRecord, so I'll have to check it out as well -- though I will say I'm more interested in the "::DBI" aspect of it all than the class thing. I'm not a firm believer of sticking inheritance models in databases.	[reply]

Replies are listed 'Best First'.

Re^3: Class::DBI -- does it get any easier?
by Anonymous Monk on Nov 12, 2004 at 19:52 UTC

I can see it would be a problem when making larger apps and apps that use existing tables, definitely. But for building new apps, it is unbelievable useful. I have one real-world app running on our intranet right now, but it's pretty light use and doesn't have that many tables to it. The "Tables" link above seems fairly similar to ActiveRecord, so I'll have to check it out as well -- though I will say I'm more interested in the "::DBI" aspect of it all than the class thing. I'm not a firm believer of sticking inheritance models in databases.

[reply]