Yeah, that is what I thought, although my personal goal is to make it as close to 100% functional as possible with DB2 so I will keep plugging away and try to make it work.
----- Original Message ---- From: David E Jones <[EMAIL PROTECTED]> To: [email protected] Sent: Friday, November 3, 2006 1:41:35 AM Subject: Re: db2 express-c and ofbiz You should be able to get away without the primary key information, I think this is only used right now to check database PK definitions against the application level ones in the entity model. That's a handy feature, but not necessary. In fact, I think there's an attribute on the datasource element to tell it to not even check the pks. -David On Nov 3, 2006, at 12:30 AM, Jason Lane wrote: > Yes, I saw in the code a TODO on the primary key section that > mentions looping through the tables to get the primary keys for > each. If I get some time I might add some code there to add that > ability. Right now on DB2 it cannot get the primary keys for the > various tables. I'm not sure if that actually will cause any > problems since the primary keys are there, OFBiz just can't see > them in that particular instance. > > ----- Original Message ---- > From: David E Jones <[EMAIL PROTECTED]> > To: [email protected] > Sent: Friday, November 3, 2006 12:46:43 AM > Subject: Re: db2 express-c and ofbiz > > > 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 >> >> >> >> > > > >
