Gaetano Mendola <mendola@bigfoot.com> writes:
> The count(*) information can be revisioned too, am I wrong ? I'm able to
> create a trigger that store the count(*) information in a special table,
> why not implement the same in a way "builded in" ?
Then every insert or delete would have to lock that count. Nobody else would
be able to insert or delete any records until you either commit or roll back.
That would lead to much lower concurrency, much more contention for locks, and
tons of deadlocks.
--
greg
