tag:blogger.com,1999:blog-5705818669612605666.post4983759376753626756..comments2024-03-28T01:38:19.526-04:00Comments on Sathya's Tech Notes: ADF DB Sequence - Using DB Trigger approachSathya AGhttp://www.blogger.com/profile/17711711259619024371noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-5705818669612605666.post-79260108647533564072014-03-07T15:44:06.349-05:002014-03-07T15:44:06.349-05:00Thanks for the post,Good explanation...Thanks for the post,Good explanation...Bhushannoreply@blogger.comtag:blogger.com,1999:blog-5705818669612605666.post-78191625648729271932014-03-06T03:24:57.739-05:002014-03-06T03:24:57.739-05:00Yes. That's the advantage of this approach. If...Yes. That's the advantage of this approach. If the use rolls back the transaction, the sequence will not be consumed.Sathya AGhttps://www.blogger.com/profile/17711711259619024371noreply@blogger.comtag:blogger.com,1999:blog-5705818669612605666.post-7861791608332475542014-03-05T02:24:22.938-05:002014-03-05T02:24:22.938-05:00Hi,
Thanks for the post.
What if the user rollba...Hi, <br />Thanks for the post.<br /><br />What if the user rollback and did not want to insert new record. Does the sequence number keep returns to its original value before user request. <br /><br />Example:<br />Imagine user press (CreateInsert Button), newly records is showing to the user with the current sequence number (let's say it is 100). Now, what if the user rollback and cancel the operation. Dose the sequence stay on 100 as the current number or its start from 101 when the user want to add new record laterAnonymoushttps://www.blogger.com/profile/03161340719132756040noreply@blogger.com