Path: csiph.com!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Cecil Westerhof Newsgroups: comp.lang.java.programmer Subject: Re: Testing the functionality of sub classes Date: Sun, 20 Aug 2017 18:13:30 +0200 Organization: Decebal Computing Lines: 23 Message-ID: <87h8x2dxp1.fsf@munus.decebal.nl> References: <87fucnh2wu.fsf@munus.decebal.nl> <87y3qffim5.fsf@munus.decebal.nl> <87pobrf855.fsf@munus.decebal.nl> <87ziaue74o.fsf@munus.decebal.nl> <87valie4xz.fsf@munus.decebal.nl> <87o9rae27u.fsf@munus.decebal.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: mx02.eternal-september.org; posting-host="a3233d099e71e24d901953f13bac9801"; logging-data="8948"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/GR9pJSq+AyQJlE4ZaPcw8/oSx9mEKeXk=" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) Cancel-Lock: sha1:s/kEY0GanHUQ/r4+fjKW+9GUC8I= sha1:qpB+ZYCeBCvfztMvjtFz1XIlDv8= X-Homepage: http://www.decebal.nl/ Xref: csiph.com comp.lang.java.programmer:37321 Arne Vajhøj writes: >> Nope, it shows that the H2 driver does follow the standards (and the >> SQLite3 driver does not). The first ResultSet is closed as it should >> be. You can do an isClosed on it. So it is not null, but displays a >> null to show you should not use it anymore. > > The contract for toString is extremely vague. > > I do not see any indication than SQLite does not follow > JDBC standard. > > Reusing result set object should be perfectly valid > per JDBC standard. In the description of Statement (copied with spelling mistakes): All execution methods in the Statement interface implicitly close a statment's current ResultSet object if an open one exists. -- Cecil Westerhof Senior Software Engineer LinkedIn: http://www.linkedin.com/in/cecilwesterhof