Oliver,
Your understanding is correct. Compatible version controls changes in
functionality between releases of the jdbc client code and has nothing
to do with the server version. So in cases like blob support where the
functionality of the driver changed in a non-backwardly compatible way
between versions 7.1 and 7.2 of the driver the compatible parameter
allows you to change back to the old way of doing things. This allows
you to use the newest version of the driver to take advantage of the new
functionality and bug fixes and gives you a window of time to upgrade
your code to convert over to the new way of doing things. It doesn't
matter what the server version is in these cases.
thanks,
--Barry
Oliver Jowett wrote:
> On Wed, Dec 17, 2003 at 07:17:43PM -0500, Kris Jurka wrote:
>
>
>>Additionally doing some testing revealed another bug with compatibilty
>>version handling. If the user does not explicitly specify a "compatible"
>>parameter it defaults to the jdbc driver version. It should instead
>>default to the server version the connection is for because a newer driver
>>can talk to older databases.
>
>
> Is this correct? I thought compatible=X meant "behave like the driver in
> version X behaved" i.e. it was there for handling incompatible driver
> changes, not server-side changes.
>
> -O
>
> ---------------------------(end of broadcast)---------------------------
> TIP 7: don't forget to increase your free space map settings
>
