Thanks to Perl Monks for identifying the length() problem and to
Tim for pointing me at other areas where it could be a problem.
And thanks to you, Martin!
Michael
Michael has confirmed that DBD::ODBC 1.24_6 fixes the problem he saw
with SQL Server XMLType columns.
1.24_6 defaults binding of XMLType parameters as SQL_WCHAR on Unicode
enabled DBD::ODBCs now and the length() issue (which turned out to be an
error in DBD::ODBC ignoring magic) is also
Michael,
When reporting issues with DBD::ODBC it is useful to know the operating system
name and version and the ODBC driver and version as this can have a big effect.
On 15/09/10 01:18, Michael Ludwig wrote:
I'm facing encoding issues in trying to make use of the XML datatype in
SQL Server
I've had some time to look at this more and would like to correct a few things.
Firstly, DBI DOES define SQL_WCHAR so if you pull in :sql_types you can used
SQL_WCHAR instead of using -8.
Also, the mystery over the length() call producing the wrong result was a
missing call to SvSETMAGIC (big
Martin,
Martin J. Evans schrieb am 15.09.2010 um 11:12 (+0100):
Michael,
When reporting issues with DBD::ODBC it is useful to know the
operating system name and version and the ODBC driver and version as
this can have a big effect.
This is on Windows XP Home SP3 using SQL Server Native
Martin J. Evans schrieb am 15.09.2010 um 17:55 (+0100):
Firstly, DBI DOES define SQL_WCHAR so if you pull in :sql_types you
can used SQL_WCHAR instead of using -8.
Yes.
Also, the mystery over the length() call producing the wrong result
was a missing call to SvSETMAGIC (big thanks to Perl
On 15/09/2010 21:11, Michael Ludwig wrote:
Martin,
Martin J. Evans schrieb am 15.09.2010 um 11:12 (+0100):
Michael,
When reporting issues with DBD::ODBC it is useful to know the
operating system name and version and the ODBC driver and version as
this can have a big effect.
This is on
Martin J. Evans schrieb am 15.09.2010 um 21:27 (+0100):
DBD::ODBC 1.24_5 uploaded to CPAN now but your mirror might take
longer for you to see.
Not there yet.
I would not get too excited as I did not try the native client yet
and don't have it at home so it will have to wait until tomorrow.
I'm facing encoding issues in trying to make use of the XML datatype in
SQL Server 2005, which I'm accessing using DBD::ODBC 1.23 and Perl 5.12.
CREATE TABLE T2 (a VARCHAR(99), u NVARCHAR(99), x XML);
Three columns here, a for single-byte characters, u for Unicode, and
x for XML.
The
