I have a class descriptor (CLASS_A) with a reference to another (CLASS_B). Both CLASS_A and CLASS_B have a property called "NAME".
-If I retrieve CLASS_A objects (using PB) with no orderby, everything is fine. -If I retrieve CLASS_A objects in the same manner, but add a "CLASS_B_REF.SOME_OTHER_PROPERTY" orderby, everything is fine. -However, if I retrieve CLASS_A objects after adding a "CLASS_B_REF.NAME" orderby, the NAME value from CLASS_B gets populated in the NAME properties of *both* the CLASS_A and CLASS_B objects! In other words, if I add an orderby to my criteria and that orderby is a referenced class with a property name that exists in both the parent class and referenced class, the referenced value is populated in both the parent object and referenced object (they get identical values). So for example, in the database, it may look like this..... TABLE_A.NAME = "FOO" TABLE_B.NAME = "BAR" But in scenario described above, I get..... CLASS_A.NAME = "BAR" CLASS_B.NAME = "BAR One other note, in my mappings, my classes are the same name as my tables and properties same names as the columns.... in case that has anything to do with it. If necessary, I'll try to provide an exact example with real mappings, sql, etc. so someone can try to reproduce the effect. I've tried this on both RC4 and RC5. I'm using MySQL. Any ideas? Thanks! __________________________________ Do you Yahoo!? New Yahoo! Photos - easier uploading and sharing. http://photos.yahoo.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
