On 07/09/11 22:34, Paolo Castagna wrote:
The original reason was that the expected usage was large(ish) initial
> load and smaller incremental changes so the basic stats (and it's only
> the relative numbers that matter) were still useful. that isn't always
> the case, and transactions are going to make it worse.
Why transactions are going to make it worse?
Is it because a transaction can be aborted? Couldn't we update stats
only when a transaction is successfully committed?
It's not a technical change - it's a change in the way apps might use
TDB. The original bulk-load and publish has relatively static stats.
Starting from empty and often adding (and deleting) content is made
easier with transactions.
Andy
