Rick Hillegas wrote:
> We already have to cross this bridge for the next release of Derby.
> DERBY-280 is a correctness bug, which while not fixed, was patched. This
> changes the behavior of a family of queries which were returning wrong
> results. What should we do:
>
> 2) Document the changed behavior in the Release Notes. If an important
> customer complains, then we can evaluate how to satisfy that customer in
> a follow-on release.
Remember this is open-source, there are no customers or "important
customers", only users and developers.
If a user doesn't like the solution they have at least two options:
- get involved in the Derby developer community
- patch the source
I prefer the first.
Dan.
|