Hi
Just a smal word to present our Eclipse plugin for
database and Ojb.
http://sourceforge.net/project/showfiles.php?group_id=106057
It is the second release news :
Produce repository, mapping and Java files (New namer
base on torque namer)
Enable to create/edit tables and fields.
Produce Torque
Hi Andy,
Andy Malakov wrote:
Hello Armin,
Thanks for quick reply.
Unfortunately problem remains in OJB_1_0_RELEASE.
I will add a test for this bug, how can we reproduce the NPE, how does
the query look like?
regards,
Armin
Please look at SqlQueryStatement [line 128]: m_root =
createTa
Hello Armin,
Thanks for quick reply.
Unfortunately problem remains in OJB_1_0_RELEASE.
Please look at SqlQueryStatement [line 128]: m_root =
createTableAlias(m_baseCld, hints=null, path="");
When above line is called for abstract class descriptor (the one that has
extent, but not mapped to a t
Hi Andy,
Andy Malakov wrote:
Hello All,
When org.apache.ojb.broker.accesslayer.sql.SqlQueryStatement.TableAlias is used
for abstract class (has extent classes declared, but not mapped to any table
itself) it may initialized with tableName=null. This situation later produces a
problem, becaus
Hi Eric,
Ferrer, Eric wrote:
There is no Oracle error in the stack track or in the spy.log.
seems this is caused by oracle 10g driver
Caused by: java.sql.SQLException: Attempt to set Escape Processing after
SQL is already processed
Please try to use Oracle9i platform settings in your
jdbc-
There is no Oracle error in the stack track or in the spy.log.
-Original Message-
From: Jakob Braeuchi [mailto:[EMAIL PROTECTED]
Sent: Saturday, December 10, 2005 3:45 AM
To: OJB Users List
Subject: Re: Oracle OJB error
hi eric,
i'm looking for the sql exception with an oracle error, so
Hello All,
When org.apache.ojb.broker.accesslayer.sql.SqlQueryStatement.TableAlias is used
for abstract class (has extent classes declared, but not mapped to any table
itself) it may initialized with tableName=null. This situation later produces a
problem, because tableName is being used for Ta
Hi,
you can find more info about this issue in thread: (9. June 2005)
ThreadLocal causing memory leak
The patch has been applied for the upcoming OJB 1.0.4 release. If you are impatient and have not the possibility to get it from CVS then you will find an
explication on how to 'manually' fix it