Rob Kinyon wrote:
I would recommend, on the first pass at least, to not worry about BEFORE
INSERT triggers. Just get:
select <SEQUENCE_NAME>.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 approach is
really common, we're not doing Oracle users any favors by punting on
this...
It's the approach that several different Oracle DBAs have given me,
plus it's recommended in their manual.
I didn't realize that was common/recommended. Make 'em both work then :)
-Todd
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Rose-db-object mailing list
Rose-db-object@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rose-db-object
