Hi,
It seems when i use a n-m relation to a subclassed object, the
sql produced by ojb is not good.
The interesting part of our mapping :
(note that the problem is because VersionJeuLimites inherits
from Version not because VersionPdS inherits also from Version.)
class-descriptor
Hi Vamsi,
sorry for the late reply.
I added an JIRA issue (maybe someone can spend time to adapt this section).
regards,
Armin
Vamsi Atluri wrote:
Hello all,
In our application we use OJBs extensively. However, we have a CLOB field
that needs to be populated within the application. I was
Hi Leigh,
Leigh Estes wrote:
We have found an interesting behavior that has only cropped up since we
updated from OJB 1.0.2 to 1.0.3. We have an object mapping defined as
follows:
class-descriptor class=com.dchoc.sphinx.entity.QuestionEntity
table=QUESTIONS
field-descriptor id=1 name=id
Hi,
It seems when i use a n-m relation to a subclassed object, the sql produced
by ojb is not good.
The interesting part of our mapping :
(note that the problem is because VersionJeuLimites inherits from Version
not because VersionPdS inherits also from Version.)
class-descriptor
Thomas,
I'v been using OJB for years now and it is the first time that I get it.
Maybe my provider changed something, i will check that out. My descriptor
looks like this for quite a while now :
!-- this connection was used as the default one within OJB --
jdbc-connection-descriptor
