Timeline for How could sequence.nextval be null in Oracle?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 4, 2013 at 20:02 | vote | accept | Corbin March | ||
| Feb 16, 2012 at 16:57 | comment | added | Corbin March |
I understand the points made. The problem exists in procs inserting into tables with and without triggers so a trigger isn't required. When a trigger exists, it simply inserts into an audit table. I've confirmed :new.the_id is untouched. I understand my question is a long shot. It is resistant to my google-fu and has several people scratching their heads here. I just figured someone might recognize the symptom (and treatment) given enough eyeballs. Thanks for taking a look.
|
|
| Feb 16, 2012 at 16:31 | comment | added | Niall Litchfield | Corbin, what I mean (and Kevin) is that something odd is going on between your code and oracle - if you run the test purely in SQL you don't get the effect. But see Phil's comment about the audit trigger (which you could try disabling). | |
| Feb 16, 2012 at 14:51 | comment | added | Corbin March | Agreed that it's likely a problem with app code or driver. I'm just curious what could cause a null nextval as a side effect. Puzzling. Thanks for the performance tip. It's good advice that I'll suggest to the team. | |
| Feb 16, 2012 at 13:35 | comment | added | Niall Litchfield | by the way a version with the traditional approach of using a trigger for the the_id column and the procedure as follows also ran quicker create or replace PROCEDURE Insert_Record3 (p_name IN dbse13142.name%type, p_userid IN dbse13142.userid%type, p_theid OUT dbse13142.the_id%type) IS BEGIN INSERT INTO dbse13142 (name, userid) VALUES (p_name, p_userid) returning the_id into p_theid; END; / | |
| Feb 16, 2012 at 11:07 | history | answered | Niall Litchfield | CC BY-SA 3.0 |