Path: csiph.com!goblin3!goblin.stu.neva.ru!news.tu-darmstadt.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: v_borchert@despammed.com (Volker Borchert) Newsgroups: comp.lang.java.programmer Subject: Re: Testing the functionality of sub classes Date: 21 Aug 2017 19:53:02 GMT Organization: Private site at Eddersheim, Germany Lines: 28 Distribution: world Message-ID: References: <87fucnh2wu.fsf@munus.decebal.nl> <87y3qffim5.fsf@munus.decebal.nl> <87pobrf855.fsf@munus.decebal.nl> X-Trace: individual.net QBd/TlX6zT5lQcfV/a1AkAb/Iv97VxSKaBAih3OR0oMDD7Vp0i Cancel-Lock: sha1:iXhiwOx3P2rIbtikGpw0uusVLPE= Xref: csiph.com comp.lang.java.programmer:37329 Andreas Leitgeb wrote: > Cecil Westerhof wrote: > > For example: when creating a new ResultSet through a Statement the > > previous generated should be closed. With the JDBC driver I use for > > SQLite3 the old ResultSet is not closed, but becomes a copy from the > > last generated. > > Are you sure about the "copy"? I'd rather expect(*) that the driver > re-uses the particular ResultSet instance and returns the same ref > again. (*: that is: based on your posted observations. Usually, > instance re-use is frowned upon, like premature optimisation, but then > again, DB driver vendors might have optimised it "well-maturely".) With Oracle's thin driver, a client's ResultSet corresponds to a server's cursor... > To verify (or disprove) it, you could run it in e.g. eclipse, jvisualvm should do, and comes with the JDK. > and see > if the same (or a new) "id" appears when you execute another query on > the same Statement. -- "I'm a doctor, not a mechanic." Dr Leonard McCoy "I'm a mechanic, not a doctor." Volker Borchert