Carl Franks wrote:
>> package Foo::Schema;
>> use base qw/DBIx::Class::Schema/;
>>
>> __PACKAGE__->declare( ... );
>>
>> 1;
>>
>> Where ... could be a data structure, a string, a filehandle, a
>> filename, or undef to read from __DATA__
>
> I like the sound of that, but how about having it point to a
> "create_tables.sql" file?
> /very/ DRY :)
Because DBIx-Class can already generate your deployment SQL for you. There's
metadata required at the ORM layer that isn't required at the database layer,
so the SQL DDL statements are never going to be sufficient - and cease to be
DRY very rapidly as you try to go cross-database anyway.
--
Matt S Trout Offering custom development, consultancy and support
Technical Director contracts for Catalyst, DBIx::Class and BAST. Contact
Shadowcat Systems Ltd. mst (at) shadowcatsystems.co.uk for more information
+ Help us build a better perl ORM: http://dbix-class.shadowcatsystems.co.uk/ +
_______________________________________________
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/
