RE : bad sql on n-m relation to subclassed object

: vendredi 10 mars 2006 19:09 À : OJB Users List Objet : Re: bad sql on n-m relation to subclassed object hi nicolas, please post the relevant parts of the repository.xml and eventually the generated sql. i hope you didn't leave the project because of ojb ;) jakob delahaye.nicolas schrieb: Hi jakob

Re: bad sql on n-m relation to subclassed object

hi nicolas, please post the relevant parts of the repository.xml and eventually the generated sql. i hope you didn't leave the project because of ojb ;) jakob delahaye.nicolas schrieb: Hi jakob, Thank for your answer. I have see an other strange thing : I have a class B that inherit from

Re: bad sql on n-m relation to subclassed object

hi nicolas, we recently fixed a problem concening findObjectByIdentity see 'OJB and the X-Files... :)' in this case the sql looked ok, but the wrong object was materialized. if the problem still persists, could yu please post a testcase so i can try to reproduce it. thanks jakob DELAHAYE

Re: bad sql on n-m relation to subclassed object

hi nicolas, you say A links to A. how is this done ? shouldn't there be a idreftoA in A as well ? jakob DELAHAYE Nicolas schrieb: hi Jakob Braeuchi I have this model : A link to A B, C, and D that inherit of A when i would like retreive a object A by findObjectByIdentity, the left out

Re: bad sql on n-m relation to subclassed object

Hi Jakob Braeuchi, The link A - A is made by an other field (linktoSelf) But i have try also without this link (A to A) and the part of query that made the left out join, link by : A.id = A.idreftoA. DB like : A [id, linktoSelft] ID is PK B [idreftoA, fielB ] idreftA is PK and FK C

Re: bad sql on n-m relation to subclassed object

hi Jakob Braeuchi I have this model : A link to A B, C, and D that inherit of A when i would like retreive a object A by findObjectByIdentity, the left out join make a link on A.id = A.idreftoA for each inherited classes. idreftoA is define as primary key and foreigner key of inherited

Re: bad sql on n-m relation to subclassed object

hi nicolas, i'm pleased the latest version works for you. could you please post the error, or give me a hint where you found discussions about the bug. jakob delahaye.nicolas schrieb: Hi jakob, Ok, it is working with 1.0.4. But if i want retreive the super class alone, a wrong SLQ query

Re: Re: bad sql on n-m relation to subclassed object

Hi jakob, Ok, it is working with 1.0.4. But if i want retreive the super class alone, a wrong SLQ query is made, I have seen on the forum that is a bug. My question is : do you know if this defect will be fixed on 1.0.5 ? Best regards Nicolas DELAHAYE hi nicolas, ojb just release 1.0.4. could

Re: bad sql on n-m relation to subclassed object

Sorry for multi posting, Otherwise, the version we use is 1.03 Jakob Braeuchi wrote: hi nicolas, i recommend not to cross-post, and to post the same message only once ;) further i recommend to tell us the version of ojb you're using. thank jakob -- Nicolas DELAHAYE

Re: bad sql on n-m relation to subclassed object

hi nicolas, i recommend not to cross-post, and to post the same message only once ;) further i recommend to tell us the version of ojb you're using. thank jakob [EMAIL PROTECTED] schrieb: Hi, It seems when i use a n-m relation to a subclassed object, the sql produced by ojb is not good.

Re: bad sql on n-m relation to subclassed object

hi nicolas, ojb just release 1.0.4. could you please try this as well ? jakob DELAHAYE Nicolas schrieb: Sorry for multi posting, Otherwise, the version we use is 1.03 Jakob Braeuchi wrote: hi nicolas, i recommend not to cross-post, and to post the same message only once ;) further i