Brandon Black wrote:
On 7/10/07, Jeff Zucker <[EMAIL PROTECTED]> wrote:
If you want to treat those oddball DBD's as
if they were not DBI-like, you could make a new
DBIx::Class::Schema::Loader::Foo. However, if your backends are in
fact DBD's, one way to support them would be to bring them up to speed
with regard to the optional DBI metadata methods [1].
Yep, the problem is that they are so oddball that they never store any
metadata other than the column names (think of a standard CSV file - no
primary key info, no column types ...). So with no metadata stored,
there's nothing for the DBI methods to query. The cool thing about the
Loader is that you can use e.g. MySQL DDL syntax to make relationships
between CSV files that have no metadata ... the example at perlmonks
works with CSV even though DBD::CSV a) doesn't understand Foreign Keys
and b) doesn't natively support three table joins. It works because I
use SQLT's MySQL parser on the DDL. Eventutally I can make the DBDs
store their DDL so that the metadata will be saved (in a schema.cfg file
or some such) but that's too much work for summetime :-).
--
Jeff
_______________________________________________
List: http://lists.rawmode.org/cgi-bin/mailman/listinfo/dbix-class
Wiki: http://dbix-class.shadowcatsystems.co.uk/
IRC: irc.perl.org#dbix-class
SVN: http://dev.catalyst.perl.org/repos/bast/trunk/DBIx-Class/
Searchable Archive: http://www.mail-archive.com/dbix-class@lists.rawmode.org/
