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

Sure does, thanks!
Christian

------------------------------------------------
Christian Cryder
Software Engineer, Rocks
Lutris Technologies, Inc.
christianc@lutris.com
------------------------------------------------
       "What a great time to be a Geek"
------------------------------------------------
 http://www.lutris.com ~ http://xmlc.enhydra.org


> -----Original Message-----
> From: owner-instantDB@enhydra.org [mailto:owner-instantDB@enhydra.org]On
> Behalf Of Peter Hearty
> Sent: Monday, November 20, 2000 10:17 AM
> To: instantDB@enhydra.org
> Subject: Re: InstantDB: Update not realized immediately (Addendum)
>
>
> Christian
>
> Is http://instantdb.enhydra.org/software/documentation/warnings.html
> relevant here?
>
> Regards
>
> Pete
>
> --
>
> Peter Hearty                         peter.hearty@lutris.com
> Lutris Technologies (UK)        http://www.lutris.com
> ----- Original Message -----
> From: "Christian Cryder" <christian.cryder@lutris.com>
> To: <instantDB@enhydra.org>
> Sent: Monday, November 20, 2000 6:55 PM
> Subject: RE: InstantDB: Update not realized immediately (Addendum)
>
>
> > Just an additional note: I just duplicated this with raw JDBC
> as well (no
> > Enhydra classes in the equation) so I'm 99.9% sure this is an IDB issue.
> >
> > Explanations welcome.
> >
> > Thanks,
> > Christian
> > ------------------------------------------------
> > Christian Cryder
> > Software Engineer, Rocks
> > Lutris Technologies, Inc.
> > christianc@lutris.com
> > ------------------------------------------------
> >        "What a great time to be a Geek"
> > ------------------------------------------------
> >  http://www.lutris.com ~ http://xmlc.enhydra.org
> >
> >
> > > -----Original Message-----
> > > From: owner-instantDB@enhydra.org
> [mailto:owner-instantDB@enhydra.org]On
> > > Behalf Of Christian Cryder
> > > Sent: Monday, November 20, 2000 10:42 AM
> > > To: InstantDB
> > > Subject: InstantDB: Update not realized immediately
> > >
> > >
> > > Hi folks,
> > >
> > > Here's something I noticed with InstantDB this morning
> (latest version).
> > >
> > > Let's say I have 2 processes connected to a database. If proc
> 2 updates
> a
> > > row, proc 1 never sees the change until it first disconnects and then
> > > reconnects to the database. For instance, here's a sample sequence:
> > >
> > > Proc 1 --> select * from ObjectID (Result: next=1000040)
> > > Proc 2 --> update objectid set next = 1000039
> > > Proc 1 --> select * from ObjectID (Result: next=1000040)
> > > Proc 1 --> Disconnect/reconnect to DB
> > > Proc 1 --> select * from ObjectID (Result: next=1000039)
> > >
> > > This doesn't seem correct. Can anyone explain this to me?
> > >
> > > Please note, I'm doing updates/queries using the Enhydra
> > > DBConnection class
> > > like this:
> > >
> > >   (Proc 1)
> > >   DBConnection conn =
> Enhydra.getDatabaseManager().allocateConnection();
> > >   ResultSet rs = conn.executeQuery("SELECT * FROM Person");
> > >
> > >   (Proc 2)
> > >   int rows = conn.executeUpdate("update objectid set next = 1000039");
> > >   conn.commit();
> > >
> > > Am I misusing the Enhydra DBConnection class? Or is something
> > > strange going
> > > on with InstantDB?
> > >
> > > Thanks,
> > > Christian
> > > ------------------------------------------------
> > > Christian Cryder
> > > Software Engineer, Rocks
> > > Lutris Technologies, Inc.
> > > christianc@lutris.com
> > > ------------------------------------------------
> > >        "What a great time to be a Geek"
> > > ------------------------------------------------
> > >  http://www.lutris.com ~ http://xmlc.enhydra.org
> > >
> > >
> > > ------------------------------------------------------------------
> > > -----------
> > > 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.
> >
> >
> --------------------------------------------------------------------------
> ---
> > 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.
> >
>
> ------------------------------------------------------------------
> -----------
> 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.

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