> using long transactions would be pretty horrible :( > long transactions should be avoided like the plague at all cost. > Especially with certain databases (like Microsofts or Sybase variants)
I never really used them myself, so that's entirely possible :-) > i would do it how igors proposes. Have multiply rows for the same data > with 1 row that is live and another row (with maybe the editting userid as > data so that you know what to get the next time) Yeah, that's a workable idea. The problem then is cleaning up the entries that never were finished, and just the fact that you're polluting your data model with administrative data. But it might be the best solution. Eelco --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
