FW: DBI/DBD won"t recognize transaction support

------_=_NextPart_001_01C68B12.D06ED7A6
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


> Greetings
>=20
> I am trying to get the perl interface to work for InnoDB tables on =
mysql v 5.0.21, perl 5.8.5, dbi 1.51, dbd 3.0004_1 on a Dell PowerEdge =
with quad dual-core Xeons running Redhat Enterprise v4. I can create an =
InnoDB table from the mysql command line, insert a row, see it's there, =
rollback, see the row is gone. But the simple script below fails:
>=20
> use DBI;
> my $user =3D 'root';
> my $pw =3D ;
> my $dbh =3D DBI->connect("DBI:mysql:database=3Dtest;host=3D127.0.0.1", =
$user, $pw, { AutoCommit =3D> 0, RaiseError =3D> 0 });
> die DBI::errstr unless $dbh;
> $dbh->disconnect;
>=20
> The DBI/DBD interface is working OK for other (non-InnoDB) scripts.
>=20
> DBI passes all it's tests except for those that complain about =
DBI::PurePerl. DBD passes all of its tests except the one that deals =
with transactions. Can anyone offer a suggestion how to isolate the =
problem? SHOW ENGINES indicates that InnoDB is indeed enabled and =
actions with InnoDB from the mysql command line work OK. Should I make =
InnoDB the default table type when I start the server? Am I simply hosed =
because of multi-threading?
>=20
> Thanks
>=20
> Mike
>=20

------_=_NextPart_001_01C68B12.D06ED7A6--

Re: FW: DBI/DBD won"t recognize transaction support

Michael Muratet US-Huntsville wrote:

Michael,

I'll take a look into this issue tomorrow. I'm working on another
release hopefully by this weekend.

Thanks!

Patrick
>> Greetings
>>
>> I am trying to get the perl interface to work for InnoDB tables on mysql v 5.0.21, perl 5.8.5, dbi 1.51, dbd 3.0004_1 on a Dell PowerEdge with quad dual-core Xeons running Redhat Enterprise v4. I can create an InnoDB table from the mysql command line, insert a row, see it's there, rollback, see the row is gone. But the simple script below fails:
>>
>> use DBI;
>> my $user = 'root';
>> my $pw = ;
>> my $dbh = DBI->connect("DBI:mysql:database=test;host=127.0.0.1", $user, $pw, { AutoCommit => 0, RaiseError => 0 });
>> die DBI::errstr unless $dbh;
>> $dbh->disconnect;
>>
>> The DBI/DBD interface is working OK for other (non-InnoDB) scripts.
>>
>> DBI passes all it's tests except for those that complain about DBI::PurePerl. DBD passes all of its tests except the one that deals with transactions. Can anyone offer a suggestion how to isolate the problem? SHOW ENGINES indicates that InnoDB is indeed enabled and actions with InnoDB from the mysql command line work OK. Should I make InnoDB the default table type when I start the server? Am I simply hosed because of multi-threading?
>>
>> Thanks
>>
>> Mike
>>
>>
>
>


--
MySQL Perl Mailing List
For list archives: http://lists.mysql.com/perl
To unsubscribe: http://lists.mysql.com/perl?unsub=gcdmp-msql-mysql-modules@m .gmane.org

Re: FW: DBI/DBD won"t recognize transaction support

Michael Muratet US-Huntsville wrote:

Michael,

I can't get this to fail. What sort of error does this throw?

Thanks!

Patrick
>> Greetings
>>
>> I am trying to get the perl interface to work for InnoDB tables on mysql v 5.0.21, perl 5.8.5, dbi 1.51, dbd 3.0004_1 on a Dell PowerEdge with quad dual-core Xeons running Redhat Enterprise v4. I can create an InnoDB table from the mysql command line, insert a row, see it's there, rollback, see the row is gone. But the simple script below fails:
>>
>> use DBI;
>> my $user = 'root';
>> my $pw = ;
>> my $dbh = DBI->connect("DBI:mysql:database=test;host=127.0.0.1", $user, $pw, { AutoCommit => 0, RaiseError => 0 });
>> die DBI::errstr unless $dbh;
>> $dbh->disconnect;
>>
>> The DBI/DBD interface is working OK for other (non-InnoDB) scripts.
>>
>> DBI passes all it's tests except for those that complain about DBI::PurePerl. DBD passes all of its tests except the one that deals with transactions. Can anyone offer a suggestion how to isolate the problem? SHOW ENGINES indicates that InnoDB is indeed enabled and actions with InnoDB from the mysql command line work OK. Should I make InnoDB the default table type when I start the server? Am I simply hosed because of multi-threading?
>>
>> Thanks
>>
>> Mike
>>
>>
>
>


--
MySQL Perl Mailing List
For list archives: http://lists.mysql.com/perl
To unsubscribe: http://lists.mysql.com/perl?unsub=gcdmp-msql-mysql-modules@m .gmane.org