On 2006-01-31 01:24:18 +0100, Patrick Galbraith wrote:
I apologise for what might seem somewhat of a bit of neglect on my part to
get
some features into DBD::mysql, features such as UTF support, some bugs in
3.0002_4. I've been super busy on some other projects, but have finished one
of
On Wed, Mar 29, 2006 at 10:53:56AM +0200, Peter J. Holzer wrote:
On 2006-01-31 01:24:18 +0100, Patrick Galbraith wrote:
I apologise for what might seem somewhat of a bit of neglect on my part to
get
some features into DBD::mysql, features such as UTF support, some bugs in
3.0002_4.
Hi,
I have subclassed DBI and override many methods including prepare, execute and
select* although they are predominantly just passed on to DBI.
If I do:
my $sth-prepare(sql);
$sth-execute;
I see the prepare and execute and pass them on to DBI.
If I do:
$dbh-selectrow_array(sql);
I see
The issue I am seeing is not quite as general as I made it sound. For
selectrow_hashref I see prepare/execute/fetch/fetchrow_hashref (as I expect) but
for selectrow_arrayref and selectrow_array I only see prepare.
Martin
--
Martin J. Evans
Easysoft Ltd, UK
http://www.easysoft.com
On 29-Mar-2006
Sir,
Please provide me the help to upgrade the latest of DBI.
I am using Oracle 9
It shows error:
Can't locate Test/More.pm in @INC (@INC contains: lib C:/paresh/Perl/lib
C:/pare
sh/Perl/site/lib .) at makefile.pl line 36.
BEGIN failed--compilation aborted at makefile.pl line
On Wed, 2006-03-29 at 05:34 -0800, Paresh Rathod wrote:
Sir,
Please provide me the help to upgrade the latest of DBI.
I am using Oracle 9
It shows error:
Can't locate Test/More.pm
You need to install Test::More.
in @INC (@INC contains: lib C:/paresh/Perl/lib
According to the docs for execute_array:
The mandatory ArrayTupleStatus attribute is used to specify a reference to
array which will receive the execute status of each executed parameter tuple.
It would appear in DBI 1.50 you can omit it:
$sth-execute_array({ });
Is it mandatory and the docs
On Wed, 2006-03-29 at 17:57 +0300, [EMAIL PROTECTED] wrote:
Please use [EMAIL PROTECTED] instead of [EMAIL PROTECTED]
I didn't use either, I replied to a post on dbi-users list. If
you're email has changed then correct it with the dbi-user list,
don't send replies like this when
On Wed, Mar 29, 2006 at 11:54:32AM +0100, Martin J. Evans wrote:
The issue I am seeing is not quite as general as I made it sound. For
selectrow_hashref I see prepare/execute/fetch/fetchrow_hashref (as I expect)
but
for selectrow_arrayref and selectrow_array I only see prepare.
Generally...
ppm 'install Test::More'
-Original Message-
From: Paresh Rathod [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 29, 2006 6:35 AM
To: dbi-users@perl.org
Subject: Upgrade.. DBI
Sir,
Please provide me the help to upgrade the latest of DBI.
I am using Oracle 9
It shows
Tim,
Thanks, I do keep forgetting about Driver.xst.
So, just to be clear. In DBI.pm, selectrow_array calls _do_selectrow which
calls prepare/execute/fetchsomething but this may be overriden by a driver
using selectrow_array in Driver.xst. If this is the case:
a) is there any way for my
Hi,
I think I may have found a bug in DBD::mysql for execute_array.
The following code demonstrates:
#!/usr/bin/perl
use strict;
use warnings;
use DBI;
use Data::Dumper;
my $dbh = DBI-connect(
'DBI:mysql:mjetest', 'xxx', 'yyy',
#'DBI:ODBC:mjetest', 'xxx', 'yyy',
) or die
On Wed, 29 Mar 2006, Garrett, Philip (MAN-Corporate) wrote:
My database has utf8 columns, server/client character sets and
collation. Yet when I call fetchrow, resulting Perl scalars do
not have the utf8 flag set. That's really annoying. Am I
supposed to call
map {
On Wed, 29 Mar 2006, Tim Bunce wrote:
On Wed, Mar 29, 2006 at 10:53:56AM +0200, Peter J. Holzer wrote:
On 2006-01-31 01:24:18 +0100, Patrick Galbraith wrote:
I apologise for what might seem somewhat of a bit of neglect on my part
to get
some features into DBD::mysql, features
On Wed, 29 Mar 2006, Mark Hedges wrote:
Hmm, for some reason this morning the Matrix has allowed the
selected characters to display correctly in the browser. This
doesn't make a whole lot of sense to me now.
The scalars still do not have the utf8 flag set, though.
This is really
On Wed, 29 Mar 2006, Mark Hedges wrote:
Hmm, for some reason this morning the Matrix has allowed the
selected characters to display correctly in the browser. This
doesn't make a whole lot of sense to me now.
The scalars still do not have the utf8 flag set, though.
This is
On Wed, Mar 29, 2006 at 09:58:16AM -0800, Mark Hedges wrote:
On Wed, 29 Mar 2006, Tim Bunce wrote:
On Wed, Mar 29, 2006 at 10:53:56AM +0200, Peter J. Holzer wrote:
On 2006-01-31 01:24:18 +0100, Patrick Galbraith wrote:
I apologise for what might seem somewhat of a bit of neglect on my
On Wed, Mar 29, 2006 at 04:49:32PM +0100, Martin J. Evans wrote:
Tim,
Thanks, I do keep forgetting about Driver.xst.
So, just to be clear. In DBI.pm, selectrow_array calls _do_selectrow which
calls prepare/execute/fetchsomething but this may be overriden by a driver
using selectrow_array
On Wed, Mar 29, 2006 at 03:57:39PM +0100, Martin J. Evans wrote:
According to the docs for execute_array:
The mandatory ArrayTupleStatus attribute is used to specify a reference to
array which will receive the execute status of each executed parameter tuple.
It would appear in DBI 1.50 you
Thanks Tim. I'm now hopefully looking in the right places.
Not seeing execute on a selectrow_array threw me initially
but it is an example of the problems I'm seeing.
I'm having a few problems accessing things at the time I want.
e.g. execute_array can be called with the parameters (which I
Tim Bunce wrote:
On Wed, Mar 29, 2006 at 09:58:16AM -0800, Mark Hedges wrote:
On Wed, 29 Mar 2006, Tim Bunce wrote:
On Wed, Mar 29, 2006 at 10:53:56AM +0200, Peter J. Holzer wrote:
On 2006-01-31 01:24:18 +0100, Patrick Galbraith wrote:
I apologise for what might seem somewhat of a bit of
On Wed, Mar 29, 2006 at 09:02:43PM +0100, Martin J. Evans wrote:
Thanks Tim. I'm now hopefully looking in the right places.
Not seeing execute on a selectrow_array threw me initially
but it is an example of the problems I'm seeing.
I'm having a few problems accessing things at the time I
Tim Bunce wrote:
On Wed, Mar 29, 2006 at 09:02:43PM +0100, Martin J. Evans wrote:
Thanks Tim. I'm now hopefully looking in the right places.
Not seeing execute on a selectrow_array threw me initially
but it is an example of the problems I'm seeing.
I'm having a few problems accessing things
Patch against dbd::mysql 3.0002_4 which demonstrates that if you prepare
a statement and execute multiple times then as soon as one execute fails
all subsequent executes fail. This obviously effects execute_array in
particular as all the tuple_status values from the failed execute
onwards show an
24 matches
Mail list logo
