> >> - InterBase have MGA since 1985
>
> MT> v1, correct?
>
> Maybe, only Jinm can tell :-)
>
> >> - Oracle have versioning (named as semi-verisioning
> >> because it have some problems with very long snapshot
> >> transactions) since version 8.0 (am I right?).
>
> MT> No earlier. Reading in the newsgroup, they say since v3 or v4
> MT> or it got extended MVCC since v4.
>
> what do you mean by v3 or v4?

Oracle v3 or v4 :-)

> MT> Although I thought it was around v7 ...
>
> not sure. I know that moving from v7 to v8
> extended database size up to 15-25% by
> metadata versioning and record versions
> (I know that versions stored in transacion log).
>
> >> - MS SQL 2005 will have versioning same as in InterBase/Firebird.
>
> MT> Not entirely sure -- it has _something_ like MGA.
>
> I have carefully read some local articles, and seems that
> MS SQL 2005 versioning copied 95% of IB/FB versioning.

I thought they only do a part of this, with "snapshot transaction",
but not for the rest?

> >> - MySQL will (? or already) have versioning ... don't know
> >> about it's implementation or limitations.
>
> MT> They have MVCC/MGA in its InnoDB storage system.
>
> already? I'm not sure about their transaction support,
> so versioning here does not mean so much. I'm wrong?

InnoDB has transaction support and Foreign Key Constraints.

With regards,

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