Re: oracle.jdbc.LobStreamPosStandardCompliant
Re: oracle.jdbc.LobStreamPosStandardCompliant
- Subject: Re: oracle.jdbc.LobStreamPosStandardCompliant
- From: "Ricardo J. Parada" <email@hidden>
- Date: Wed, 22 Sep 2010 09:47:18 -0400
On Sep 21, 2010, at 11:49 PM, Mike Schrag wrote: http://osdir.com/ml/webobjects-dev/2010-05/msg00169.htmlI know I'm 4 months late, but I just wanted to follow up with this and say "you're fine setting this" ... Essential what's happening here is that OraclePlugIn calls setBinaryStream(0) and the actual JDBC specification says that's 1-offset, not 0-offset, so Oracle's JDBC driver secretly bumps it to 1 internally when that property is set. It throws an exception if the property isn't set.
Thanks. Yes we've been running with:
oracle.jdbc.LobStreamPosStandardCompliant=false
since I sent out that email.
One other thing you may run into with 11g -- you should make sure that your "DATE" columns explicitly set valueType = "D". If you don't specify a valueType, you'll hit a problem where 11g now ignores the oracle.jdbc.V8Compatible property.
Hmmm... I don't recall if we've had problems with "DATE" columns. I think we're using the "date" prototype from ERPrototypes, which by the way, I don't see it having valueType = "D" :
{ columnName = ""; externalType = DATE; name = date; valueClassName = NSCalendarDate; },
But if we're hitting the problem, I don't know yet. Do you have a description of the problem?
Thanks, Ricardo
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden