Jonathan,
The test that fails works fine for me.
What ODBC driver are you using?
Strangely, what DBD::ODBC is saying is that you bound an in/out parameter of
max size 50 then changed it to 51 but the code in 20SqlServer has a hard-wired
50 so somewhere a long the line the 50 that got into
With mysql 3.0002_4:
perl -e 'use DBI; my $dbh =
DBI-connect(dbi:mysql:xx, ppp,qqq);
print supported\n if ($dbh-can(primary_key_info));'
does not print supported for me.
The same with DBD::ODBC does print supported.
So, I'd guess primary_key_info is not supported in DBD::mysql.
Martin
Hi list.
I believe I have tripped a DBD::Oracle bug in the way it binds utf8
parameters. If I create a statement and execute it with a non-utf8
parameter, it works. If I then execute that *same sth* with a utf8
parameter (scalar with UTF8 flag on), I receive the following error:
ORA-01460:
-Original Message-
From: Garrett, Philip (MAN-Corporate)
[mailto:[EMAIL PROTECTED]
Sent: Friday, March 03, 2006 1:50 PM
To: dbi-users@perl.org
Subject: DBD::Oracle error when switching between utf8 and non-utf8
[snip]
DBI: 1.4.1
Probably obvious, but I meant 1.41.
Philip
Hi,
MySQL supports transactions on INNOB tables. Does this mean that DBI
on MySQL has transaction support? Do I have to set any variables on MySQL
to support the transactions does support.
mary anderson
Others on this list may know more about the MySQL specifics, but in
general DBI has transaction support for all databases.
You turn it on in DBI with this:
$dbh-{AutoCommit} = 0;
Or by setting AutoCommit to 0 in the connect() parameters.
Consult the man pages for more information.
-Will
As Will writes, I use transactions within DBD::mysql with MySQL 5 but
ONLY if using innodb tables. i.e. you need to add the innodb to the
create table defn.
Typically, I ignore Autocommit and do a $dbh-begin_work then
a $dbh-commit - works fine so long as you remember transaction
timeout which
