Based on your description of the column problem I'd guess it is
similar to another problem we talked about a bit ago. OFBiz sends
null for the table name so that it can get back all column info in a
single pass, rather than doing 700 round trips to the database. The
time difference for most databases is a few seconds instead of a few
minutes, so it makes a very big startup difference. I'm not sure this
is the problem, but I'm guessing it is based on your description and
that error message.
-David
On Nov 2, 2006, at 2:23 PM, Jason Lane wrote:
Well, I actually found the proper way to fix this, without changing
code. It turns out that the schema name needs to be all upper case
since DB2 treats it as an ordinary identifier that must be
uppercase. After I fixed that I was able to get the table names
without changing any code.
Now it seems thee is something going on with the column info
portion. When it tries to get the column information I get an error:
"Invalid getIndexInfo call: null not allowed for table name.. Not
checking columns."
I guess I will need to debug and step through until I find why it's
null. I'm guessing the ArrayList that holds the table names was
maybe not resized to remove null identifiers and so it's getting a
null on one of the calls, but I'll have to take a look.
Unless of course if someone else has seen this and knows what I'm
doing wrong.
----- Original Message ----
From: David E Jones <[EMAIL PROTECTED]>
To: [email protected]
Sent: Thursday, November 2, 2006 9:56:33 AM
Subject: Re: db2 express-c and ofbiz
On Nov 2, 2006, at 7:38 AM, Jason Lane wrote:
One thing I have not figured out yet. It seems that ofbiz supports
sending properties for database connections (via a Properties
object) but where can I change or add different properties? I
wanted to play around with changing the cursor sensitivity, driver
type, etc. I assume that the properties can be placed in a config
file somewhere (either properties or XML) but the entityengine.xml
doesn't seem to be the place.
These can usually be added on the JDBC URI.
-David
