Bryan Pendleton wrote:
Oystein Grovlen - Sun Norway wrote:
Oh, I did not notice this. I tried to run batchUpdate with
DerbyNetClient, but this still fails. I guess that means that beetle
5561 is still an issue
Perhaps this is worthy of a JIRA issue of its own, something along the
lines of:
- if you run jdbcapi/batchUpdate with DerbyNetClient, it fails
with symptom XXX. As part of fixing this bug, the test case
for DERBY-1292 should be moved from jdbcapi/prepStmt.java to
jdbc/batchUpdate.java so that it fits more cleanly with the
other tests in the test suite.
Then we could move ahead with James's fix to DERBY-1292 in the interim.
Would that be an acceptable way to separate the two but not lose track
of the preferred solution?
Good proposal, Bryan. I will file a Jira issue for this after the week-end.
--
Øystein
