Thomas Franke wrote:
> org.apache.ojb.broker.PersistenceBrokerSQLException: SQLException during the
> execution of the query (for de.mhr.wis.DBAdapter.rawdata.analyses.Logbuch):
> Cannot write sorted rows.
We got it. It seems with the latest driver we solved the problem. The exception
above occurs
Hi Armin,
> It could be a jdbc-driver problem
It seems that it is really a driver problem.
We changed the driver to the latest version and the exception changed too. ;)
The exception comes directly from the jdbc driver.
Here is the stack trace in full:
11.11.2005 18:06:41 [ERROR]
de.mhr.wis.DBAd
Hi Armin,
> I setup a test against the latest version of OJB_1_0_RELEASE branch
> using maxDB and hsql with an empty table.
That's great, thanks.
> All tests pass without problems. So we have isolate your issue (not
> really ;-)): It could be a jdbc-driver problem or a bug in an older
> version o
Hi Thomas,
I setup a test against the latest version of OJB_1_0_RELEASE branch
using maxDB and hsql with an empty table.
public void testObjectByQuery_1() throws Exception
{
String dummy = "nothing_to_find";
Criteria criteria = new Criteria();
criteria.addEqualTo("name", du
Hello there,
if we call
log = (Logbuch) broker.getObjectByQuery(query);
we get a NoSuchElementException.
At the moment because of a fresh database we know there aren't any records.
We're using Informix Dynamik Server 9.4 and Informix JDBC.3.00.JC1 driver.
I could imagine it is rather a jdbc dri
Hi Armin,
> Would it be possible to use INTEGER in Informix too? Ask this because I want
> to move #prepareNextValProcedureStatement implementation method to
> PlatformDefaultImpl.
I could do that but I'll explain you why I did this decision.
First of all the SequenceManagerStoredProcedureImpl#bu
