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

If one looks at the docs from Sun java.sql.ResultSet, this can be noted:

"A ResultSet object is automatically closed when the Statement object that
generated it is closed, re-executed, or used to retrieve the next result from a
sequence of multiple results. "

I guess idb is in closing of the pre ResultSet when you are making a statement
and gets the  exception.


Regards,
Martin




Einar Valen <einar.valen@scase.no> on 19-07-2000 10:57:44

Please respond to instantDB@enhydra.org

To:   instantdb@enhydra.org
cc:
Subject:  InstantDB: Empty result sets after an SQLException



When the database thows a SQLException at me, for violating a null
constaint or an illegaly formated date or whatever, all resultsets seems
empty after that. Until I reconnect to the database. Then everything
works fine.
Is there any other way around this?

I am new to InstantDB. Have have only been trying it out  for a few
days. Greatful for any suggestions.

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