
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: Possible bug?

To: <instantdb@enhydra.org>
Subject: InstantDB: Possible bug?
From: "David Corbin" <dcorbin@imperitek.com>
Date: Thu, 3 May 2001 20:34:25 -0400
Reply-To: instantDB@enhydra.org
Sender: owner-instantDB@enhydra.org

When setting a timestamp object on a PreparedStatement, if the value you're setting is null, it generates a NullPointerException. I realize that there is a setNull() method, but shouldn't this be taken care of in the setTimeStamp()?

David Corbin

Prev by Date: Re: InstantDB: Date Types and In Clause fail.
Next by Date: InstantDB: Chinese Support
Prev by thread: Re: InstantDB: Date Types and In Clause fail.
Next by thread: InstantDB: Using SMALLCHAR in InstantDB
Index(es):
- Mail Date Index
- Mail Thread Index