...and then write a language construct like (in ruby I'd write): with_number_do : { ... their code here... }
have a table of used IDs lock the table, read the last item, incr by one, save to table, perform your other action, save that to DB, then close the transaction on the table of IDs?
-
-
-
...LOL, which is EXACTLY your lambda idea!
- Show replies
New conversation -
-
-
This Tweet is unavailable.
-
yeah, this is absolutely going to EXPOSE any circular dependencies you have. If every object gets a monotonically increasing ID, and you nest with_id { ... with_id { ... you're F-ed
- Show replies
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.