NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
an endless discussion thread about what features to include.
-- Jarkko Hietaniemi
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Database Abstractions (Score:2)
The benefits of database abstractions such as Class::DBI are obvious, but the downsides of these technologies can hamper scalability. On one hand, with the CDBI approach, we have a clear mapping of classes to tables, but the databases for which these have been designed are relational when classes tend to be heirarchical. This not only forces developers to accept awkward design constraints (subclassing a table can be an act of supreme masochism), but with the wrong design, it can also limit scalability.
Re:Database Abstractions (Score:1)
> more ad hoc queries. Writing custom SQL for each
> one becomes problematic
Why is this problematic? If you have to write non-trivial queries to get information out of a database, how else would you expect to be able to do that?
This isn't meant to be a snippy response - I'm truly interested in what other sorts of ways this sort of thing could be done.
Tony
Reply to This
Parent