| Subject | Re: [firebird-support] Unique keys without gaps (was: Keyviolation on Primary/Unique key constraint INTEG_55/30 on table(s) ) |
|---|---|
| Author | Sándor Tamás (HostWare Kft.) |
| Post date | 2006-03-14T12:57:48Z |
> In a concurrent system, you cannot guarantee "no gaps", even with yourCan you explain, why is it so bad idea?
> semaphore (which is a bad idea, verging on evil).
I know, transaction can be bottleneck, I have to guarantee that getting the
next value has to be immediately before posting records, in one short
transaction.