RE: :Oracle V 1.16 & Oracle type 187 not explicitly supported

On Mon, 5 Dec 2005 17:24:44 +1100, Steve Baldwin wrote:

Hi Steve

> with your data. I think the problem is that DBD::Oracle has not
> yet absorbed some of the newer data type functionality of Oracle.

Interesting. I see the Changes file for DBD::Oracle V 1.15 says timestamp
support was added, but I'll take your advise and recreate all tables using=
date
and see what happens.

--
Cheers
Ron Savage, ron@savage.net.au on 5/12/2005
http://savage.net.au/index.html
Let the record show: Microsoft is not an Australian company

RE: :Oracle V 1.16 & Oracle type 187 not explicitly supported

Hi Folks

The problem was the intervention of NFS.

For a command line script (eg a CGI script run from the command line),
DBD::Oracle::VERSION returned 1.16, but for a real CGI script (i.e. the same=

script run thru a browser) it was only 1.14, since CGI scripts run on a
different machine.=09Sigh.

Case closed.
--
Cheers
Ron Savage, ron@savage.net.au on 7/12/2005
http://savage.net.au/index.html
Let the record show: Microsoft is not an Australian company