Re^2: Rose::DB and DBIx

I haven't done anything with Rose-DB yet, so I can't comment on the learning curve. From discussions in #dbix-class and on the DBIx::Class mailing list I remember that RDB's speed advantage comes from less methods who contain much more logic. While this brings a speed gain (less method calls) it sacrifices easy extensibility, which is one of DBIx::Class' big advantages.

Ordinary morality is for ordinary people. -- Aleister Crowley

Comment on Re^2: Rose::DB and DBIx

Replies are listed 'Best First'.
Re^3: Rose::DB and DBIx by siracusa (Friar) on Jan 19, 2007 at 17:14 UTC
Well, it depends on what you're extending. For example, RDBO has a very flexible framework for defining new column types, encapsulating inflate/deflate, custom DBI bind_param()s, type-specific attributes, and custom SQL for select, query, and insert into a single logical unit. DBIx::Class is still working on some of these features, and the lack of a standardized way to add support for new column types has led to less support for "rich" column type handling. As in any large collection of code, there are really only a few performance-critical parts of RDBO that are aggressively optimized. The vast majority of the code is quite modular.	[reply]

Replies are listed 'Best First'.

Re^3: Rose::DB and DBIx
by siracusa (Friar) on Jan 19, 2007 at 17:14 UTC

Well, it depends on what you're extending. For example, RDBO has a very flexible framework for defining new column types, encapsulating inflate/deflate, custom DBI bind_param()s, type-specific attributes, and custom SQL for select, query, and insert into a single logical unit. DBIx::Class is still working on some of these features, and the lack of a standardized way to add support for new column types has led to less support for "rich" column type handling.

As in any large collection of code, there are really only a few performance-critical parts of RDBO that are aggressively optimized. The vast majority of the code is quite modular.

[reply]