It probably is if the column is set to NOT NULL in the database and you
are storing objects with it nulled out.
-Brian
On Jan 1, 2004, at 10:06 PM, Gunnar Hilling wrote:
Is it possible that the reason is a change in my datamodel: I added an
additional ojb collection, backed by a DList. My "old"
Sorry folk, I think the reason was that I had Implicit Locking set to
false...
Perhapts nevertheless interesting to know the cause...
Regards,
-Gunnar
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mai
I've developed a simple code snippet to reproduce the error:
Produkt prod=(Produkt)res.get(0);
Zertifikat zert=new Zertifikat();
TextData xml=new TextData("xml", "tach");
TextData plain=new TextData("plain", "tach");
Is it possible that the reason is a change in my datamodel: I added an
additional ojb collection, backed by a DList. My "old" objects in the db
don't have this dlist. I assume, ojb tries to load the dlist and
doesn't find it.
Am I right? How can I fix this??
Thanks a lot.
-Gunnar
-
Hello,
Could please anyone help me in finding the reason for the following error:
It occurs when creating a bunch of new objects ...
[org.apache.ojb.broker.accesslayer.JdbcAccessImpl]
ERROR: SQLException during the execution of the insert (for a
org.apache.ojb.odmg.collections.DListEntry_2): ERRO
n with a value of "Oracle", all
was fine.
-Original Message-
From: Michael Hart [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 29, 2003 8:13 PM
To: 'OJB Users List'
Subject: RE: Strange Error
> So what is the SQL being generated? Don't know - can't get any OJB
> So what is the SQL being generated? Don't know - can't get any OJB output
> even when setting things to DEBUG in the OJB.properties file and we have
> never been able to get spy to work for us.
I think the latest version of OJB.properties and PoorMansLoggerImpl.java in
the repository have fixed
You can use P6SPY to get the generated SQL, or you can use Oracle DBA
Studio to see the SQL in the same fashion as MS SQL Profiler.
Jason
On Thu, 2003-05-29 at 11:58, Shannon Ewing wrote:
> We are running into a strange error. We are receiving a "ORA-00933: SQL
> command not pro
We are running into a strange error. We are receiving a "ORA-00933: SQL
command not properly ended" exception only when we are using Oracle 8 using
a jndi data source and creating a query that does a join. The following is a
code example:
Criteria criteria = ne