[CDBI] mysql compress support

Matt S Trout dbix-class at trout.me.uk
Tue Aug 30 15:04:01 BST 2005


On Tue, Aug 30, 2005 at 01:40:01PM +0100, William Ross wrote:
> 4. investigate the alternative ORM solutions, especially John  
> Siracusa's Rose::DB, which I think is turning into a better choice  
> than cdbi. It already has a much better object structure and looks  
> like it will offer the sort of hook you need to tweak column  
> retrieval very easily. I haven't used it properly yet so can't be sure.

Rose::DB has a reasonable interface and is very fast, but it's making the same
SQL-liberally-sprinkled-in-the-code mistakes that the Tangram project is
currently working hard to refactor out (and making fantastic progress too
- you should drop in and see how they're getting on as well).

For example (from Rose::DB::Object::MetaData) -

sub insert_sql
{
  my($self) = shift;

  no warnings;
  return $self->{'insert_sql'} ||=
    'INSERT INTO ' . $self->fq_table_sql . "\n(\n" .
    join(",\n", map { "  $_" } $self->column_names) .
    "\n)\nVALUES\n(\n" . join(",\n", map { "  ?" } $self->column_names) .
    "\n)";
}

I somehow doubt this is going to help you very much ...

DBIx::Class, OTOH, already provides the vast majority of the Class::DBI
feature set and in fact it's CDBICompat modules allow it to pass the vast
majority of the Class::DBI 0.999 test suite. And we're working hard to make
it as abstracted and extensible as humanly possible. Consider reposting you
question to the dbix-class list (there's a link to the listinfo from the wiki
linked in my signature) and seeing what the user community (and half-dozen
active developers) come up with ...

-- 
     Matt S Trout       Specialists in perl consulting, web development, and
  Technical Director    UNIX/Linux systems architecture and automation. Mail
Shadowcat Systems Ltd.  mst (at) shadowcatsystems.co.uk for more information

 + Help us build a better perl ORM: http://dbix-class.shadowcatsystems.co.uk/ +




More information about the ClassDBI mailing list