Thomas,
I've looked at the 2.00 code. Thanks for the improvements here. The
explicit nextval() exception is helpful.
However, I still consider it an open issue that you can't declare a
specific select statement as being one that modifies. For example, you
could write a custom procedural function that modifies during a select,
and there is no way to detect that automatically.
So, I think manual intervention must be supported. I see it looking like
this:
$dbh->selectrow_array($sql, { mx_modifies => 1 }, @bind);
The DBI spec allows drivers to have their own attributes here, as long
as they have a prefix unique to the driver.
Given the above syntax, I check could made for "mx_modifies" that would
override automatic detection.
Mark
