On Wed, Jun 29, 2011 at 03:28:19PM +0100, Martin J. Evans wrote:
> Don't know however, I am inclined to change the error to a warning as Tim
> suggested. It simplifies things for people who might be calling fetch on a
> non-select. However, it isn't going to happen soon unless someone screams for
Show, don't tell. Also, it's a little shorter now.
BEGIN THING TO INSERT
=head3 On use of non-C SQL in C methods
While some drivers support statements other than C in the
above-listed convenience functions, others do not: driver support for this
facility is not defined by the DBI interface stand
On 29/06/11 14:34, David Nicol wrote:
On Wed, Jun 29, 2011 at 3:02 AM, Martin J. Evans
wrote:
BEGIN THING TO INSERT
=head3 On use of non-CSQL in Cmethods
When you really don't know if the statement you have in a
variable is going
to be a C or not, unrolling the process into
C,C
On Wed, Jun 29, 2011 at 3:02 AM, Martin J. Evans
wrote:
>> BEGIN THING TO INSERT
>> =head3 On use of non-C SQL in C methods
>>
>> When you really don't know if the statement you have in a
>> variable is going
>> to be a C or not, unrolling the process into
>> C,C, and
>> a C called within a
On Wed, Jun 29, 2011 at 09:02:27AM +0100, Martin J. Evans wrote:
> On 24/06/11 16:17, David Nicol wrote:
>
> perl -le 'use DBI; my $h = DBI->connect(); my $s = $h->prepare("create table
> fred (a int)"); $s->execute; my $r = $s->fetch;'
> DBD::ODBC::st fetch failed: no select statement currently
On 24/06/11 16:17, David Nicol wrote:
On Sat, Jun 11, 2011 at 12:51 PM, Tim Bunce wrote:
Patch welcome.
Tim.
here's a revised new paragraph, to go right before the =head3 C.
BEGIN THING TO INSERT
=head3 On use of non-C SQL in C methods
While some drivers support statements other than C
