On Fri, 19 Dec 2003, Antonio Gallardo wrote: > A similar thread is in the dev list: > > http://nagoya.apache.org/eyebrowse/ReadMsg?listId=106&msgNo=5522 > > Best Regards, > > Antonio Gallardo > > > Thomas Dudziak dijo: > >> I had some stange values aut objects since updated to RC5. > >> After some debuging I found out that I got illegal values at attributes > >> which does not match with the database. For example I got a attribute > >> at tahe object with the value 15 where a 0 is stored at the > >> corresponding > >> database row. > >> The solution was the sort order at the repository_user.xml. > >> My repository_user.xml was auto generated and did not represent the > >> correct > >> order of field-descriptor id's. I former time this worked. > >> Now it seems that the id's must have the correct order. After sorting > >> the > >> repository everything worked fine. All the fields had the correct id so > >> it was not a real mapping error. I just thougt that OJB uses the > >> field-descriptor for mapping the column. > >> I'll now sort my repository an think that everything will work after > >> that. > >> Will this problem be fixed? I thing trusting in the position is > >> dangerous. > > > > Could you perhaps post the repository_user.xml and the java source files ? > > > > Tom >
Ah I see. Well, in the XDoclet module at least I could ensure that the foreignkeys/inverse-foreignkeys are in the same order as the primarykeys. Tom --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
