On 9/14/2010 12:41 AM, John R Pierce wrote:
On 05/18/10 9:41 AM, Charles Jardine wrote:
On 17/05/10 23:05, John R Pierce wrote:
I've built DBD-Oracle-1.24 along with Perl 5.12.0 and DBI-1.611 for IBM
AIX 6.1 TL05 (oslevel = 6100-05-01), with Oracle 10.2.0.4, using IBM XL
C v11.1 + the latest
On 09/14/10 5:35 AM, John Scoles wrote:
Did this ever get tested and entered into the DBD-Oracle release ?
This issue has surfaced at work, so I can probably try testing your
patches some time in the next week or so, possibly on both sparc and
aix/power platforms, but if someone else has
On 9/14/2010 9:17 AM, John R Pierce wrote:
On 09/14/10 5:35 AM, John Scoles wrote:
Did this ever get tested and entered into the DBD-Oracle release ?
This issue has surfaced at work, so I can probably try testing your
patches some time in the next week or so, possibly on both sparc and
On 09/14/10 6:58 AM, John Scoles wrote:
On 9/14/2010 9:17 AM, John R Pierce wrote:
Sorry, I meant, the make test problems with t/58object on big endian
machines like Sparc, IBM Power
Ok that clears it up a little.
I am not sure if it was fixed yet.
Give the latest trunk version a try
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
Jerry,
Hi there - I'm the maintainer of DBD::mysql
The verbiage going to your log looks like what you would see if you set
the DBI trace level to 2 or greater. I've double-checked my code and any
debug I print is indeed only occurring in a block where if trace is set
to 2 or greater it would
