It looks like the DbMerger in 3.0M4 isn't properly detecting whether
NULL is allowed for columns when using MySQL. Is this another issue that
has already been fixed in trunk?
Does it seem reasonable to expect the MySQL adapter to know that MyISAM
doesn't support db-enforced FKs? I don't have the ability to use InnoDB
on one of my target platforms, so DbMerger inevitably complains about
the relationships every time I check the schema.
Regards,
Scott
This archive was generated by hypermail 2.0.0 : Thu Aug 28 2008 - 13:35:57 EDT