Re: PreparedStatement parameters and mutable objects

On Fri, 9 Jan 2004, Oliver Jowett wrote:

> > I'm saying that doing it this way will likely expose buggy code, which
> > we will end up having to figure out why it doesn't work, when the user
> > says "my code used to work, and now it doesn't", plus they don't send us
> > code to look at.
>
> How far do we go to support buggy code though? If we can't make this
> sort of change, we lose several opportunities for optimization.

I don't think you can label this as buggy code unless you can point to the
spec and say where it is disallowed.  It is certainly something that looks
dangerous and is unlikely to be written by the average developer, but that
doesn't make it illegal.  I lean towards the notion that when I say setXXX
that's the time the value must be saved because that's certainly more
intuitive and specific than "sometime later when the driver decides to."

Kris Jurka