Re: [cx-oracle-users] Antw: Bad conversion of a unicode value?

[Jim P. <uni...@gm...>]

On Nov 29, 2007 1:37 PM, Anthony Tuininga <ant...@gm...>
wrote:

> Not everyone is going to want to switch wholesale to unicode
> immediately -- the amount of pain that would cause is considerable. I
> would agree that long term, that is the way to go, but some
> intermediate steps should probably be taken. I am thinking that it
> might work to do the following:
>
> Add a connection constructor parameter that specified that __all__
> strings should be returned as unicode objects, not string objects.
> This parameter would default to False to get the current behavior --
> string objects returned (fixing whatever is causing the problem right
>

I think that would be a fine solution.


> now). It would likely be reasonable to return unicode for nvarchar2
> data regardless of this setting but I'd appreciate some feedback on
> that.
>

I would be somewhat concerned that existing code might break if we
change the return type without user intervention.  But that said,
I don't actually have any existing code that interfaces with NCHAR
types.


> I've also considered some setting that would allow you to specify
> unicode for certain columns but perhaps it would be better to go all
> unicode or the hybrid I suggested above, and not confuse matters by
> adding that capability. Thoughts?
>

I would not need that.   In my case, I'm either doing 100 Unicode, or
100 ASCII.  All my legacy systems are ASCII only, and eveything new
is Unicode all the way.

Jim Patterson