Hello all, So I've been working with Rose::DB::Object::Loader for the last two days, and I think I've found a bug with how foreign keys are handled with a MySQL 5.0 database (InnoDB tables).
In short, when RDBO::Loader->make_classes() calls $meta->auto_initialize(), and a foreign key relationship exists with the table, a second copy of the object is created, but with a broken ::MetaData object within. I first noticed this when calling make_modules(), and it would blow up when attempting to create ::Manager classes. I'm still trying to create a simple test case to demonstrate it. It's definitely related to the presence of foreign keys in the database, but so far the stripped-down schemas I've built don't replicate the issue. Has anyone seen/heard of this before? If so, any insight as to what's going on? If not, I'll go back to trying to come up with a reproducible test case. Thank you, Peter ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Rose-db-object mailing list Rose-db-object@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rose-db-object
