Make your own free website on Tripod.com

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


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

InstantDB: Concurrent access and database integrity


Greetings,

I'm in the process of evaluating InstantDB and have downloaded and
tried out both versions, 3.13 and 3.14 beta. Using the sampe.prp
as my database and a modified version of commsql.java found in
Examples, I created a table called temp as follows:

    create table temp (name varchar(32))

>From here, I started two commsql sessions and carried out the following
sequence:

1. commsql session 1: <select * from temp>    no records found

2. commsql session 2: <insert into temp values ('joe')>

3. commsql session 2: <commit>

4. commsql session 2: <select * from temp>    the record 'joe' was
returned

5. commsql session 1: <select * from temp>    no records found

So my question is "Are there parameters I should be configuring to
enable databas integrity, or is it the case that InstantDB is unable to
handle concurrent update from different sessions??"

Thanks!

DN

-----------------------------------------------------------------------------
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.