On 2014-02-28, at 12:32 PM, Chuck Hill wrote: > Jumping 40 from 37427 to 37467 is a little suspicious. Is there an increment > > 1 on this sequence? It could be that EOF has a cached value out of sync > with the database.
increment is 1. > > Or is the database sequence out of sync with the data in the table? how can this happen? I started up the app from my machine and created the scenario in a very few steps. > Try re-creating the sequence. I don't have access to production tables/sequences and so I wanted to see if there was something at my end that I could "fix" before speaking with the DBA. > > Is anything else writing to this database besides EOF? nope. > > Chuck > > > On 2014-02-28, 6:07 AM, "Calven Eggert" wrote: > > I have a table A that has a one to many relationship to table B. (A->>B) At > the time A is created a user may choose to create multiple B records before > they all get saved. > > Problem is that the B records are causing a "unique constraint" error. The > first sequence number is always an already chosen ID in the table. > > Here is a snippet of the code generated: > > SELECT JOBS_NOTES_SEQ.NEXTVAL FROM DUAL > SELECT JOBS_NOTES_SEQ.NEXTVAL FROM DUAL > > INSERT INTO JOBS_NOTES(NOTES_SUBMITTED_BY, NOTES_HYPERLINK, > NOTES_USER_VISIBLE, NOTES_JOB_ID, NOTES_SUBMITTED_DATE, NOTES_DESCRIPTION, > NOTES_ID, NOTES_ATTACHMENT_NAME) VALUES (?, NULL, ?, ?, ?, ?, ?, > ?)1:204(submittedby), 2:"Y"(uservisible), 3:14456(jobid), 4:2014-02-27 > 13:34:27(submitteddate), 5:"2"(notesdescription), 6:37427(notesid), 7:"eyetv > serial number.rtf"(attachmentname)>: > INSERT INTO JOBS_NOTES(NOTES_SUBMITTED_BY, NOTES_HYPERLINK, > NOTES_USER_VISIBLE, NOTES_JOB_ID, NOTES_SUBMITTED_DATE, NOTES_DESCRIPTION, > NOTES_ID, NOTES_ATTACHMENT_NAME) VALUES (?, NULL, ?, ?, ?, ?, ?, > ?)1:204(submittedby), 2:"Y"(uservisible), 3:14456(jobid), 4:2014-02-27 > 13:34:27(submitteddate), 5:"2"(notesdescription), 6:37467(notesid), 7:"eyetv > serial number.rtf"(attachmentname)>: > > Next exception:SQL State:23000 -- error code: 1 -- msg: ORA-00001: unique > constraint (CRE_MASTER.SYS_C001646) violated > > The number 37467 is correct but the first number 37427 is not because it is > an already existing primary key. huh? > > Anyone have any suggestions? Why is the first number invalid and why is the > second one valid? > > Calven > >
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
