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 version. It also states you can *not* store Unicode in the NCHAR datatype until Oracle 9i. On May 18, 1:23 pm, Kent Bower <[email protected]> wrote: > 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 5/18/2010 1:17 PM, Michael Bayer wrote: > > > > > 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: > >> ============================= > >> 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<[email protected]> 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 [email protected]. > >>> To unsubscribe from this group, send email to > >>> [email protected]. > >>> 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 [email protected]. > >> To unsubscribe from this group, send email to > >> [email protected]. > >> 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 [email protected]. > To unsubscribe from this group, send email to > [email protected]. > 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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en.
