On Thu, 13 Dec 2007, Altaf Malik wrote:
> JDBC is causing the connection to close on executing a simple COPY query
> which the driver does not support. The code shows that driver throws an
> exception however explicitly the connection is not closed. Consider the
> following case.
The JDBC driver doesn't even understand enough of the COPY protocol to
ignore it. Perhaps we could respond to any copy requests with copyfail,
but it would make more sense to me to look at integrating the copy patch.
So, I'm not sure what your complaint is. Do you want the driver to be
able to continue after a copy operation is issued or do you just want a
better error message? How would client code be better able to handle a
"Connection has been closed behind the scenes because something illegal
was done" vs an IOException.
Kris Jurka
