Hi all, For context, I'm working on DBIx::Class::Schema::Loader, which is an automagic loader for the DBIx::Class object<->relational mapper - it examines a live $dbh and constructs matching classes and relationships between them.
I'm trying to (as much as possible) get away from having explicit support for individual DBD's, and use generic standarized methods documented in DBI.pm in standard ways, so that it can work with any DBD which supports those methods, even ones we never planned for. This means making use of DBI methods like "tables", "primary_key_info", "foreigh_key_info", etc where possible in place of custom DBD-specific SQL statements. One method that I'd like to see, but which doesn't exist yet, is a "unique_key_info" similar to "primary_key_info", which after being released in the DBI dist, the DBD authors could work on supporting like they do "primary_key_info". Has this idea been shot down before? Is anyone already working on it? Would you mind me working up a patch for this and sending it in? -- Brandon
