Randal - I believe you misread my original message. No class referenced begins with 'Rose::DB'.
Rather, it appears that '::<relationship-name>' is appended to the name of the current class. So in class X with a child class 'X::Y', if one names a relationship 'Y', a name clash occurs. Frankly, I haven't delved deeply into all of the innards to determined that such is the case but renaming the relationship 'Y' to 'Z' resolves the problem. Randal L. Schwartz wrote:
"Philip" == Philip Dye <[EMAIL PROTECTED]> writes:Philip> This is probably well documented somewhere but I wasn't aware of it after Philip> using Rose::DB for over a year so others may find this useful. The easy solution is to have a reserved prefix for all Rose::DB subclasses and Rose::DB::Object subclasses. I've been using "My::App"::DB and "My::App::"::DBO.
------------------------------------------------------------------------- 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
