John Siracusa wrote:
4) The information schema is going to make you drool
Does DBD::Oracle support all of DBI's various *_info() methods
correctly? That alone would make auto-init 90% done, since the
default Auto.pm implementation just uses DBI's native introspection.
All we'd have to add i
John Siracusa wrote:
Either way, after the insert, I'll need a way to get the value that
was used--and do so in a concurrency-safe way. What's The Oracle Way
to do that?
In my experience, it's best way is to select the nextval from the
sequence before doing the insert, and then providing tha
Rob Kinyon wrote:
I would recommend, on the first pass at least, to not worry about BEFORE
INSERT triggers. Just get:
select .nextval from dual;
working before the insert statement, where SEQUENCE_NAME is specified by
the user.
Yeah, that sounds the simplest. But if the trigger-based
