On Thu, 26 Apr 2007, Octavian Rasnita wrote:
We could work to improve this in the long term. What would be most
helpful would be specific examples of badly-roundtripped column
definitions for a given vendor, and what they should have looked like
in order to be correct. Then we can get to figuring out whether each
case is a question of Loader not interpreting the database correctly,
a disagreement on column metadata standards, or ->deploy not writing
it out correctly.
In the short term, you're probably best off fixing it yourself by
editing the files though, sorry.
Ok, thank you.
On the long term, you can consider the example I gave. I am using MySQL and
DBIx::Class::Schema::Loader sets a "size => 10," parameter for the date, time
and datetime fields, but it shouldn't set it, or SQL::Translator should not
use that field for re-creating the SQL.
I have also seen that an enum field is not exported with its elements by
DBIx::Class::Schema::Loader.
SQL::Translator supports those, so that should be an easy fix.
As for the date field, was it a date type, a datetime, or what? Sounds odd
for it to have a size..
btw you can use $schema->create_ddl_dir to get the sql it would have
deployed, and fix it up from there.
Jess
_______________________________________________
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/[email protected]/
