Re: FW: [cpan #1764] AutoReply: Throwing an DBI::st exception fails u sing DBD::Oracle

[David Wheeler]

On Tuesday, November 5, 2002, at 06:20  AM, James.FitzGibbon wrote:

The error that comes back to the application is a plain string rather than
an object, and
the string contains information about why the exception-throwing mechanism
failed, not about
the event which caused the exception-throwing mechanism to be invoked in the
first place.

Right. This is because it appears the DBD::Oracle doesn't support the CursorName attribute and the DBI isn't supplying a valid default. There are a number of issues with attributes in the DBI, and the DBI developers are aware of them. Hopefully those issues will be addressed soon. More information is available here:

http://archive.develooper.com/dbi-dev@;perl.org/msg01507.html

In the meantime, I wonder if I should wrap the exception creation in Exception::Class::DBI in an eval {} and then report when the driver is misbehaving vis a vis attributes. Thoughts?

Regards,

David

--
David Wheeler AIM: dwTheory
[EMAIL PROTECTED] ICQ: 15726394
http://david.wheeler.net/ Yahoo!: dew7e
Jabber: [EMAIL PROTECTED]