> >> This SELECT Count(*) problem is really incredible. I can understand
> >> concurent
> >> transactions see different versions of the same table. Why is it
> >> difficult for every
> >> of these versions to also have their own row count ?
> >
> > Because such count would have to be kept in system tables, and it would
> > mean versioning system tables - which has proven to be tricky so far.
>
>
> How about letting the system tables reflect the base version of the table

and

> put the per-transaction row-count toghether with the version-specific data

of

> the table ?

No offence, but this only makes sense if you do a "select count(*) from
table".

That is: no specific columns (cause then the result can be different), no
WHERE
clause.

Why go through all this trouble for something that is, per transaction,
hardly in use?

Martijn Tonies
Database Workbench - tool for InterBase, Firebird, MySQL, NexusDB, Oracle &
MS SQL Server
Upscene Productions
http://www.upscene.com
My thoughts:
http://blog.upscene.com/martijn/
Database development questions? Check the forum!
http://www.databasedevelopmentforum.com