Oops, my bad, I didn't notice you that statement changed NVARCHAR2 to
NVARCHAR:
Here is that result:
=============================
SQL> SELECT CAST('test unicode returns' AS NVARCHAR(60)) AS anon_1
FROM DUAL
2 ;
SELECT CAST('test unicode returns' AS NVARCHAR(60)) AS anon_1 FROM
DUAL
*
ERROR at line 1:
ORA-00907: missing right parenthesis
=============================
On May 18, 12:15 pm, Kent <k...@retailarchitects.com> wrote:
> > SELECT CAST('test unicode returns' AS NVARCHAR(60)) AS anon_1 FROM DUAL
>
> > then it seems like either that fails directly, or it fails when the client
> > gets a hold of it. See what happens with that statement. Not sure that
> > Oracle 8 has NVARCHAR which might be the issue.
>
> Please see the beginning of my previous post, that is the statement
> creating the "ORA-12704: character set mismatch"
>
> So, you intend to change exc.DBAPIError to Exception? (That is
> actually exactly what I had just done as a workaround until I heard
> back from you)
>
> --
> You received this message because you are subscribed to the Google Groups
> "sqlalchemy" group.
> To post to this group, send email to sqlalch...@googlegroups.com.
> To unsubscribe from this group, send email to
> sqlalchemy+unsubscr...@googlegroups.com.
> For more options, visit this group
> athttp://groups.google.com/group/sqlalchemy?hl=en.
--
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To post to this group, send email to sqlalch...@googlegroups.com.
To unsubscribe from this group, send email to
sqlalchemy+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/sqlalchemy?hl=en.
