Stories
Slash Boxes
Comments

NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

use Perl

All the Perl that's Practical to Extract and Report

Database Abstractions More | Login | Reply

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Without JavaScript enabled, you might want to use the classic discussion system instead. If you login, you can remember this preference.

Database Abstractions (Score:2)

by Ovid (2709)

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:2)
  
  by rafael (2125) <{rgarciasuarez} {at} {gmail.com}> on 2004.08.06 10:41 (#33140) Homepage Journal
  
  I'm sure object-oriented databases are (at least in some design cases) worth looking at. Too bad there is no (to my knowledge) good OSS implementation of an OODMBS.
  
  Reply to This
  
  Parent
  - Re:Database Abstractions (Score:2)
    
    by Ovid (2709)
    
    I thought that Postgres can double as an object database, complete with table leve inheritence. I've never played with those features, though.
    - Re:Database Abstractions (Score:2)
      
      by acme (189)
      
      Nah, it's relational but with some features. The inheritance [postgresql.org] doesn't really help that much.

Get More Comments

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.