Ignore everything below
unicode_for_unicode = False
for Oracle lower than 9?
in previous post, I meant to delete those lines
--
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
On May 18, 2010, at 11:31 AM, Kent wrote:
cx_Oracle-5.0.2
This is what is causing the error:
===
SELECT CAST('test unicode returns' AS NVARCHAR2(60)) AS anon_1 FROM
DUAL
*
ERROR at line 1:
ORA-12704:
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
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
Sorry, I meant NVARCHAR2.
SELECT CAST('test unicode returns' AS NVARCHAR2(60)) AS anon_1 FROM DUAL
works ? or no ?
On May 18, 2010, at 12:17 PM, Kent wrote:
Oops, my bad, I didn't notice you that statement changed NVARCHAR2 to
NVARCHAR:
Here is that result:
No, this is what was causing ORA-12704: character set mismatch:
SQL SELECT CAST('test unicode returns' AS NVARCHAR2(60)) AS anon_1 FROM
DUAL;
SELECT CAST('test unicode returns' AS NVARCHAR2(60)) AS anon_1 FROM DUAL
*
ERROR at line 1:
ORA-12704: character set mismatch
On
There is a fairly short Oracle-published white paper on Unicode
support here:
http://www.oracle.com/technology/tech/globalization/pdf/TWP_AppDev_Unicode_10gR2.pdf
It does state that starting with Oracle7 there was Unicode support and
lists a table of Oracle version, Character set and Unicode
It specifically says NCHAR is not usable *for unicode* until Oracle
9i. (Showing my ignorance here: are you certain NVARCHAR2 uses
NCHAR? Seems logical to me.)
The white paper further states: No Unicode character set is supported
as the national character set prior to Oracle 9i. I believe the
latest patch - also try not specifiying use_ansi=False, it should detect that
now
On May 18, 2010, at 2:04 PM, Kent wrote:
It specifically says NCHAR is not usable *for unicode* until Oracle
9i. (Showing my ignorance here: are you certain NVARCHAR2 uses
NCHAR? Seems logical to me.)
Connected to:
Oracle8i Enterprise Edition Release 8.1.7.4.0 - Production
With the Partitioning option
JServer Release 8.1.7.4.0 - Production
Session altered.
SQL SELECT CAST('test unicode returns' AS VARCHAR(60)) AS anon_1 FROM
DUAL
2 ;
ANON_1
Sorry, posted too quickly, I'll get the rest of the results you asked
about...
On May 17, 4:56 pm, Kent k...@retailarchitects.com wrote:
Connected to:
Oracle8i Enterprise Edition Release 8.1.7.4.0 - Production
With the Partitioning option
JServer Release 8.1.7.4.0 - Production
Session
what do you get for engine.dialect.supports_char_length,
engine.dialect.server_version_info ?
On May 17, 2010, at 4:56 PM, Kent wrote:
Connected to:
Oracle8i Enterprise Edition Release 8.1.7.4.0 - Production
With the Partitioning option
JServer Release 8.1.7.4.0 - Production
Session
I think it is using the other select:
Connected to:
Oracle8i Enterprise Edition Release 8.1.7.4.0 - Production
With the Partitioning option
JServer Release 8.1.7.4.0 - Production
Session altered.
SQL SELECT
13 matches
Mail list logo
