That's funny, I just read about this today... See Tim Bunce's
tutorial from the Perl 3.0 Conference. I think it will answer some of
your questions...
Actually I couldn't find it from 99 but here is one from 2004.
http://search.cpan.org/src/TIMB/DBI_AdvancedTalk_2004/index.htm
Shawn
--
On 11/14/06, Steve Green <[EMAIL PROTECTED]> wrote:
Robert Hicks wrote:
> How is it best to catch errors when doing DBI stuff in web applications?
> Wrap the insert "code" in an eval statement? Croak or die statements? I
> am thinking eval because I can set autocommit to "off" and then do
> rollb
Robert Hicks wrote:
How is it best to catch errors when doing DBI stuff in web applications?
Wrap the insert "code" in an eval statement? Croak or die statements? I
am thinking eval because I can set autocommit to "off" and then do
rollbacks if $@ has an error.
The PrintError, RaiseError, a
I have a couple forms for an in-house application. The user fills out
the fields and then submits which update a back end Oracle database.
I have looked for examples but can't really find anything.
How is it best to catch errors when doing DBI stuff in web applications?
Wrap the insert "code"
