Hi,
On 2001.06.26 16:45:46 -0400 marc fleury wrote:
> |I don't think I understand what you are suggesting. However...
> |
> |Are you familiar with the lock-free versioning/ optimistic locking
> scheme
> |used in interbase/firebird?
> |
> |transactions are numbered sequentially when they are started.
> |
> |Each record (version) includes the transaction id of the last change to
> it.
> |
> |When you query information (within a transaction), you get the record
> |version with the largest transaction id <= your transaction id.
>
> yes ! this is what I asked for a couple of weeks ago, on a suggestion by
> Farid of CPW (Vinay's collegue), versioning the records for long running
> transactions and optimistic locking with distributions that have low rw
> MAKES TOTAL SENSE.
>
> However we can do it at the container level, not even at the db level
>
Yes, I was trying to point out that interbase/firebird has been doing this
successfully for 15 years, we can have our container do it too, here's an
algorithm
Someone mentioned that there "might" be dbs using optimistic locking:
interbase/firebird is one such.
As an aside, this versioning idea of Jim Starkey is the reason
interbase/firebird exists. It allows a production database to generate
meaningful reports: the report runs in a transaction that only sees the
data present when the report started, yet production transactions can
freely modify all the data in the db without affecting the report.
david jencks
> marcf
>
>
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-development
>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
