cx_Oracle currently only supports SQLT_TIMESTAMP for Oracle 9i and
above. I don't remember any more why that was the case (since I see
the definition in the Oracle 8i headers) so if you are feeling
ambitious you can try removing that restriction and seeing if any
problems occur. I don't spend a lot of time in Oracle 8i any more and
the number of other people using Oracle 8i has dropped considerably as
well so I'm not likely to spend any time on this. If you really need
this and provide me a patch, though, I'll integrate it. :-)
On 1/17/06, copal <co...@dr...> wrote:
> hahaha...i'm such a dummy sometimes. too much staring into vim. found t=
he
> rest of the types...now i just need to figure out why this is failing...
>
> sorry for my own confusion.
>
>
> On 1/17/06, copal <co...@dr...> wrote:
> > i have compiled cx_Oracle-4.1.2 on solaris for Oracle 8.1.6, but am
> getting the following error when performing a simple query:
> >
> > --- snip ---
> >
> > cx_Oracle.NotSupportedError: Variable_TypeByOracleDataType: unhandled d=
ata
> type 187
> >
> > --- snip ---
> >
> > a quick grep through $ORACLE_HOME/rdbms/demo/ocidfn.h
> shows type 187 as SQLT_TIMESTAMP, but looking though the StringVar.c fil=
e
> shows only 4 Oracle types listed: SQLT_CHR, SQLT_AFC, SQLT_BIN.
> >
> > have i missed something incredibly mundane, or does this module (the on=
ly
> python one listed on oracle's site) really not support datatypes as
> rudimentary as timestamps?
> >
> > incredibly confused - any help would be greatly appreciated.
> >
>
>
|
