db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kathey Marsden <kmarsdende...@sbcglobal.net>
Subject DERBY-213 IRC chat
Date Fri, 27 May 2005 16:08:42 GMT
This morning there was an IRC chat regarding DERBY-213.
    kmarsden    (Kathey - California)
    Bogomip_   (Phillip - New York)
    bernt           (Bernt - Norway)


Phillip and I are working on DERBY-213 using  a virtual incarnation of
the  pair programming practices of Extreme programming outlined at
http://en.wikipedia.org/wiki/Pair_programming. This means we make our
tests first and work closely together towards a solution.  Makes for
chatty IRC.

The Chat

 The full transcript is attached for those wishing to drill deeper.  
We talked about a  general strategy for fixing this bug and took the
steps outlined below.

 1) Confirm this a bug. 
      Looking at the javadoc for ResultSet we agreed that this looks
like a bug. 
       We should not close the result set if we fetch past the last row.

 2) Get a stand alone repro
      Phillip  agreed to work on this. He will make  a repro program 
that we can run for all frameworks.
       e.g.   derby213 [derby|derbynet|derbynetclient]
     Phillip will post to the list so that others can use it when fixing
bugs to check all  frameworks.
3) Add the test case to an existing test
      We talked about how it is better to add our case to an existing
test than create a new one.
      We looked at the testing framework, the different directories
store,jdbcapi, etc under functionTests/tests and also
       at the suites and looked at how to figure out if a test runs
under network server. 
      We decided we would add our case to jdbcapi/resultset.java  and
noted  the *three* masters that we will have to update when we change
the test.
 4) Check the embedded behaviour.
 5) Think of other related cases we want to test
     Phillip will think about that.
 6) Add those to the test.
 7) Start thinking of how to fix

Phillip will work on the repro and we will meet again 5am PST on
Tuesday, May 31. 



View raw message