On 03/02/2011 10:01, Tim Bunce wrote:
On Wed, Feb 02, 2011 at 03:52:00PM +, Martin J. Evans wrote:
[...]
So, I think DBI works fine right now (given slight pod change) and
don't want to complicate it or worse, break peoples existing code.
Great! :)
DBD:: Oracle on the other hand does not
On Wed, Feb 02, 2011 at 03:52:00PM +, Martin J. Evans wrote:
>
> [...]
>
> So, I think DBI works fine right now (given slight pod change) and
> don't want to complicate it or worse, break peoples existing code.
Great! :)
> DBD:: Oracle on the other hand does not but I believe John has alread
On 02/02/2011 10:52 AM, Martin J. Evans wrote:
The argument seems to have got confused here between what DBI does, what it
says it does and DBD::Oracle (which does neither). I don't want (and don't
think) any change (other than in pod) in DBI is necessary. The thread started
with my observati
The argument seems to have got confused here between what DBI does, what it
says it does and DBD::Oracle (which does neither). I don't want (and don't
think) any change (other than in pod) in DBI is necessary. The thread started
with my observations of differences between DBI and DBD::Oracle wit
On 02/02/2011 7:15 AM, Tim Bunce wrote:
On Tue, Feb 01, 2011 at 09:02:26PM +, Martin J. Evans wrote:
On 01/02/2011 20:50, Tim Bunce wrote:
On Tue, Feb 01, 2011 at 10:58:14AM -0500, John Scoles wrote:
My only concern is when it does error (no matter what the setting of
AutoCommit) you alwa
On Tue, Feb 01, 2011 at 09:02:26PM +, Martin J. Evans wrote:
> On 01/02/2011 20:50, Tim Bunce wrote:
> >On Tue, Feb 01, 2011 at 10:58:14AM -0500, John Scoles wrote:
>
> >>My only concern is when it does error (no matter what the setting of
> >>AutoCommit) you always get unef;
> >Umm, yes. Retu
On 01/02/2011 20:50, Tim Bunce wrote:
On Tue, Feb 01, 2011 at 10:58:14AM -0500, John Scoles wrote:
On 01/02/2011 10:48 AM, Tim Bunce wrote:
On Mon, Jan 31, 2011 at 08:39:40PM +, Martin J. Evans wrote:
I imagine most DBDs [if not all] that implement execute_array
[Just a reminder that dr
On Tue, Feb 01, 2011 at 10:58:14AM -0500, John Scoles wrote:
> On 01/02/2011 10:48 AM, Tim Bunce wrote:
> >On Mon, Jan 31, 2011 at 08:39:40PM +, Martin J. Evans wrote:
> >>I imagine most DBDs [if not all] that implement execute_array
> >[Just a reminder that drivers can opt to implement just
>
On 01/02/2011 11:04 AM, Martin J. Evans wrote:
On 01/02/11 15:50, John Scoles wrote:
On 01/02/2011 10:44 AM, Tim Bunce wrote:
On Sun, Jan 30, 2011 at 05:46:49PM +, Martin J. Evans wrote:
push @$tuple_status, [ $sth->err, $sth->errstr, $sth->state ];
so I guess the pod should sa
On 01/02/11 15:50, John Scoles wrote:
> On 01/02/2011 10:44 AM, Tim Bunce wrote:
>> On Sun, Jan 30, 2011 at 05:46:49PM +, Martin J. Evans wrote:
>>> push @$tuple_status, [ $sth->err, $sth->errstr, $sth->state ];
>>>
>>> so I guess the pod should say:
>>>
>>> "If the execution of a tu
On 01/02/2011 10:48 AM, Tim Bunce wrote:
On Mon, Jan 31, 2011 at 08:39:40PM +, Martin J. Evans wrote:
I imagine most DBDs [if not all] that implement execute_array
[Just a reminder that drivers can opt to implement just
execute_for_fetch() and use the DBI's default execute_array() method,
On 01/02/2011 10:44 AM, Tim Bunce wrote:
On Sun, Jan 30, 2011 at 05:46:49PM +, Martin J. Evans wrote:
push @$tuple_status, [ $sth->err, $sth->errstr, $sth->state ];
so I guess the pod should say:
"If the execution of a tuple causes an error, then the corresponding status
array
On 01/02/11 15:44, Tim Bunce wrote:
> On Sun, Jan 30, 2011 at 05:46:49PM +, Martin J. Evans wrote:
>>
>> push @$tuple_status, [ $sth->err, $sth->errstr, $sth->state ];
>>
>>so I guess the pod should say:
>>
>>"If the execution of a tuple causes an error, then the corresponding
>> stat
On Mon, Jan 31, 2011 at 08:39:40PM +, Martin J. Evans wrote:
> I imagine most DBDs [if not all] that implement execute_array
[Just a reminder that drivers can opt to implement just
execute_for_fetch() and use the DBI's default execute_array() method,
which then calls execute_for_fetch().]
> t
On Sun, Jan 30, 2011 at 05:46:49PM +, Martin J. Evans wrote:
>
> push @$tuple_status, [ $sth->err, $sth->errstr, $sth->state ];
>
>so I guess the pod should say:
>
>"If the execution of a tuple causes an error, then the corresponding
> status array element will be set to
>a ref
On 30/01/2011 18:02, John Scoles wrote:
One other thing I was picking up on is the case if you have
autocommit on and RaiseError off
I this case it if there was a an error while running in list mode it
will allways return undef. Where looking at the spec one might expect
to see undef and XX wh
On 30/01/2011 17:46, Martin J. Evans wrote:
Hi,
I'm still working on and off with execute_array problems hoping to get
DBI and the spec to match and also investigating if the current
implementation covers all possibilities. I've now written a simple
test to see if it complies with the specifi
One other thing I was picking up on is the case if you have
autocommit on and RaiseError off
I this case it if there was a an error while running in list mode it
will allways return undef. Where looking at the spec one might expect
to see undef and XX which would be the # ot records effected?
A
Hi,
I'm still working on and off with execute_array problems hoping to get
DBI and the spec to match and also investigating if the current
implementation covers all possibilities. I've now written a simple test
to see if it complies with the specification (and will include it in
DBD::ODBC) an
19 matches
Mail list logo
