InstantDB Project
About InstantDB
Project Mail Lists
Short History
Reporting Bugs
Screen Shots
3rd Party Examples
FAQs

Software
Downloads
Documentation
CVS Repositories
Roadmap
License

About Enhydra.org
Who We Are
News, Articles & Events
Getting Involved
Contact Us

Community
Demos
Contributions
Resources
Case Studies
On The Edge! -NEW-
Commercial Vendors

> Does it means, that "a single write" lock is also implemented.

On a table - yes, there can be one writer at a time. This has always been
the case. It is the throughput of readers which should improve.

> And second question: how to specify shared read lock (READ_UNCOMMITED
means
> no locks at all ?)

The new tables locks will eventually allow the remaining transaction modes
to be implemented, but only as time becomes available to do this.

In the meantime, in the serializable mode, InstantDB will automatically
select read locks for selects and write locks for updates and deletes, with
appropriate queuing of connections when they must wait for access. The main
upshot of this is that two connections can do selects simultaneously without
being queued.

Regards

Peter Hearty
Lutris Technologies (UK)
----- Original Message -----
From: "Daniel HERLEMONT" <yats@onetelnet.fr>
To: <instantDB@enhydra.org>
Sent: Saturday, August 26, 2000 2:46 PM
Subject: Re: InstantDB: Please help me


> Peter.
>
> In your last beta version you mentionned that read and multiple locks are
> now possible at table levels
> Does it means, that "a single write" lock is also implemented.
> And second question: how to specify shared read lock (READ_UNCOMMITED
means
> no locks at all ?)
> Thanks.


-----------------------------------------------------------------------------
To unsubscribe from this mailing list, send email to majordomo@enhydra.org
with the text "unsubscribe instantdb" in the body of the email.
If you have other questions regarding this mailing list, send email to
the list admin at owner-instantdb@enhydra.org.