From the latest docs:
AL16UTF16 = valid for NCHAR columns (CSID=2000)
UTF8 = valid for NCHAR columns (CSID=871), deprecated
AL32UTF8 = valid for NCHAR and CHAR columns (CSID=873)
-and-
Both UTF8 and AL32UTF32 can be used in NLS_LANG and NLS_NCHAR.
On Tue, Feb 14, 2006 at 11:00:33AM -0500, Paul G. Weiss wrote:
From the latest docs:
AL16UTF16 = valid for NCHAR columns (CSID=2000)
UTF8 = valid for NCHAR columns (CSID=871), deprecated
AL32UTF8 = valid for NCHAR and CHAR columns (CSID=873)
-and-
On 6-Feb-06, at 5:10 PM, Tim Bunce wrote:
On Mon, Feb 06, 2006 at 05:53:18AM -0800, Gisle Aas wrote:
Tim Bunce [EMAIL PROTECTED] writes:
I agree. Any chance yould you patch lib/DBI/DBD.pm to add in a
section
describing what driver authors need to do?
Is this enough?
That's great. I
Matt Sergeant [EMAIL PROTECTED] writes:
On 6-Feb-06, at 5:10 PM, Tim Bunce wrote:
On Mon, Feb 06, 2006 at 05:53:18AM -0800, Gisle Aas wrote:
Tim Bunce [EMAIL PROTECTED] writes:
I agree. Any chance yould you patch lib/DBI/DBD.pm to add in a
section
describing what driver authors
On 14-Feb-06, at 6:20 PM, Gisle Aas wrote:
There isn't currently a DBI_VERSION to test against. DBIXS.h does
define DBIXS_VERSION and this could have been incremented, but
PERL_NO_GET_CONTEXT need to be defined before this file is included.
If DBIXS_VERSION was moved to a different header file