Re: oracle.jdbc.LobStreamPosStandardCompliant
Re: oracle.jdbc.LobStreamPosStandardCompliant
- Subject: Re: oracle.jdbc.LobStreamPosStandardCompliant
- From: Mike Schrag <email@hidden>
- Date: Wed, 22 Sep 2010 12:34:36 -0400
>> 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?
So ... it may or may not actually be a problem, but I believe you're getting times in your dates, so you might not be able to do exact comparisons easily in your fetches?
http://databaseperformance.blogspot.com/2009/02/java-data-types-and-oracle-2.html
ms _______________________________________________
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