Re: strange problem using DATE fields from coldfusion/MX (jdbc)

it is the issue you suspect! when I set the class path to use the older jdbc (classes12.zip) this problem went away.

however, I cannot go back to that version since these drivers do not support updating CLOB fields with > 4K data... this is why we went to the latest JDBC drivers.

I will ask coldFusion, but its an uphill battle to talk to these guys ever since they were gobbled by Adobe.

anything anything else I might try ?

is there any alternative in the market to Oracle JDBC, which does not cost zillions, like what DataDirect is asking?

Yoram

joeNOSPAM_at_BEA.com wrote:
> Yoram Ayalon wrote:
> > Joe,
> >
> > I hope you can help me, since I am stuck between Oracle and Adobe, each
> > blaming the other...
> >
> > I tried to add the parameters to the connection string, the obvious way
> > was Data Sources section of the ColdFusion, which is where you define
> > all the parameters to the JDBC driver. they have a section calls
> > "connection string", under "advanced settings", which was empty, and I
> > added the string you specified. no luck. I noticed that after some
> > time, either a reset of ColdFusion or a reboot, these settings get
> > erased.
> >
> > these are the settings on the machine as reported by coldFusion. in the
> > summary of the data source you don't see the connection string.
> >
> > I am no Java expert. I see no other place where to configure the JDBC
> > connection and add to it the connection parameter.
> >
> > the JDBC driver we are using is the oracle 10g, ojdbc14.jar
> >
> > Java and JVM
> > ===============
> > SNIIPPED > >

>
> Ok, two things:
> 1 - Ask ColdFusion how to set driver-specific properties, such as in
> the standard JDBC:
>
> Properties p = new Properties();
> p.put("user", "scott");
> p.put("password", "tiger");
> p.put("oracle.jdbc.V8Compatible", "true");
> conn =
> DriverManager.getConnection("jdbc:oracle:thin:@dbdevelop:1521:FDEV12",
> p );
>
> 2 - Try substituting an old version of Oracle's driver instead of the
> ojdbc14.jar.
> Try an 8.1.7 version of their classes12.zip, and see if it works
> without the
> new property. That will prove it's the issue I suspect.
>
> Joe Weinstein at BEA Systems
Received on Wed Jul 19 2006 - 11:12:00 CDT