On 7/10/07, Jeff Zucker <[EMAIL PROTECTED]> wrote:
I am preparing to add the ability to attach metadata to DBDs that subclass DBD::File. This will mean that DBI metadata methods such as primary_key() and column_info() will be available and also that other modules like DBIx::Class and Class::DBI will have access to the metadata.
Sounds good to me :) It would be really cool if all of the traditional DBD's would step up to the plate and fully implement all of the DBI metadata methods as well (the full list DBIx::Class::Schema::Loader cares about are: tables, primary_key, column_info, type_info, foreign_key_info, and statistics_info (really only care about unique keys in particular from that one)). The ones we're working around the lack of currently (of course, I haven't been good about keeping up with the very latest releases on some of these, perhaps there's been progress since I last looked): DBD::SQLite - missing most of them DBD::mysql - primary_key (? may actually work, we fetch manually right now as part of the same query necessary to get uniques), foreign_key_info, statistics_info DBD::Pg - statistics_info (I patched this into their trunk, just not released yet) DBD::Oracle - statistics_info (rest are sometimes a bit oddball compared to other DBDs in their args/returns, but at least work) DBD::DB2 - statistics_info Other "normal" DBDs haven't even been looked into seriously, but if all of the metadata methods are available and work somewhat like the norm, they may "just work" without us explicitly going out of our way to support them anyways. -- Brandon
