Path: csiph.com!news.redatomik.org!aioe.org!.POSTED!not-for-mail From: =?UTF-8?Q?Arne_Vajh=c3=b8j?= Newsgroups: comp.lang.java.programmer Subject: Re: Testing the functionality of sub classes Date: Sun, 20 Aug 2017 12:28:45 -0400 Organization: Aioe.org NNTP Server Lines: 22 Message-ID: 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> <87h8x2dxp1.fsf@munus.decebal.nl> NNTP-Posting-Host: PBuS014lhzVyHjLbXmo/ZQ.user.gioia.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Complaints-To: abuse@aioe.org User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 Content-Language: en-US X-Notice: Filtered by postfilter v. 0.8.2 Xref: csiph.com comp.lang.java.programmer:37322 On 8/20/2017 12:13 PM, Cecil Westerhof wrote: > 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. It is exactly because of this that I think reuse is valid. Arne