Re^3: Why did DBIC overtake CDBI?

[davorg]

I know that Class::DBI::Loader will automatically load tables, columns and relationships. But does it, for example, automatically turn DATETIME columns into DateTime objects[1]? Or use column types to determine valid values for attributes?

The talk is a bit badly organised. The examples are all in Class::DBI (as that's what I was using when I originally wrote the talk) but the lists of items that an ORM should handle shouldn't be taken as a list of things that Class::DBI doesn't do. If anything the talk is a reaction to the number of obvious things that ActiveRecord doesn't do.

As I said in the presentation at YAPC, the talk is misnamed. Even when I first wrote it, it should have been called "What's Wrong With Some Current ORM Implementations". These days, it should really be called something like "Things To Look For When Choosing An ORM".

[1] The key word here being "automatically". I know you can use the inflate/deflate functionality, but as far as I know you need to set that up explicitly.

[siracusa]

I know that Class::DBI::Loader will automatically load tables, columns and relationships. But does it, for example, automatically turn DATETIME columns into DateTime objects[1]? Or use column types to determine valid values for attributes? [...]

[1] The key word here being "automatically". I know you can use the inflate/deflate functionality, but as far as I know you need to set that up explicitly.

FWIW, Rose::DB::Object will do this for you—and not just for DATETIME columns. It'll also turn BIT columns into Bit::Vector objects, TIME (or DATETIME HOUR TO (MINUTE|SECOND)) columns into Time::Clock objects, Postgres arrays (e.g., INT[]) into Perl arrays, BOOLEAN columns into 1 or 0 (regardless of whether the db uses "f", "false", "F", or whatever), BIGINT columns into Math::BigInt objects, and so on. (It'll also detect ENUM fields and constrain them to the valid set of values, validate dates and times, etc.)

As I said in the presentation at YAPC, the talk is misnamed. Even when I first wrote it, it should have been called "What's Wrong With Some Current ORM Implementations". These days, it should really be called something like "Things To Look For When Choosing An ORM".

Indeed :)

[perrin]

It does some of that, but not all. For example, Class::DBI::mysql lets you do this:

__PACKAGE__->autoinflate(dates => 'Time::Piece');

It can also retrieve the accepted list of values for an ENUM column. Tim Bunce posted some code that went further to add automatic value checking based on column type, but it was never formally released as a module.

These days I would advise people to use one of the newer ORMs instead, but Class::DBI's weaknesses are mostly in the SQL generation area, not in auto-discovery.