Re^3: Toggling dbi attribute within a connection?

Matt,
First, DELETE is not delete. Second, can you provide a minimal example of the code that you can't get to work per the docs (using naked blocks for scopes).

Cheers - L~R

Comment on Re^3: Toggling dbi attribute within a connection?

Replies are listed 'Best First'.
Re^4: Toggling dbi attribute within a connection? by ikegami (Patriarch) on May 12, 2005 at 16:29 UTC
%$dbh is tied, so the delete translates to a DELETE.	[reply]
Re^4: Toggling dbi attribute within a connection? by JupiterCrash (Monk) on May 12, 2005 at 15:46 UTC
The error complains about 'DELETE', yes, but I am calling 'delete'. `delete $dbh->{RaiseError};` [download] Minimal example of code as follows: `# at this point RaiseError is off as per default connection { local $dbh->{RaiseError} = 1; LABEL_START_TRANSACTION1: eval { # prepare the sql statement $sth = $dbh->prepare($sql); # execute the sql statement $sth->execute(); }; } if ($@) { .. handle the error }` [download] But at this point, right below where this code ends, dbi calls still act as if I have RaiseError turned on. Matt	[reply] [d/l] [select]