Kristian Waagan wrote:
On 28.05.10 16:03, Rick Hillegas wrote:
Hi Kristian,
Thanks for your detailed explanation of this bizarre and confusing
behavior. I can imagine that this inconsistency is very frustrating
to our users.
Each of the options you are considering will create backward
compatibility problems for some applications. I agree with Knut that
silent behavior changes are worse than noisy ones. I think that we
could talk ourselves into an incompatible behavior change if the
javadoc explicitly says that the behavior is undefined.
However, I don't see much value in moving from one inconsistent
behavior to another. If we want to tackle this confusion, then I
would recommend that we define the behavior explicitly in the javadoc
and make all of the DataSources conform to the defined behavior.
So my advice would be to not touch the code yet. Instead, file a JIRA
based on your detailed explanation of the problem. Then let the
community discuss what the best solution is.
Hi Rick,
Finally took the time to create a Jira for this :)
See DERBY-4719 [1].
Regards,
Thanks.
