On Feb 9, 2008, at 12:20 PM, Ken Johanson wrote:
But given the recent and dramatic example of 8.3's on-by-default
stricter typing in functions (now not-autocasting), I worry that
kind of change could happen in every minor version (8.4 etc).
You need to *know* your software if you're using
On Mon, 2008-02-11 at 09:09 +0100, Peter Eisentraut wrote:
Ken Johanson wrote:
Is there anything now, or in the works, for compatibility emulation? For
example to setup my session to act like 8.2 and allow less-strict
typing.
The best way to ensure 8.2 compatibility is to use 8.2. But
Ken Johanson wrote:
Is there anything now, or in the works, for compatibility emulation? For
example to setup my session to act like 8.2 and allow less-strict
typing.
The best way to ensure 8.2 compatibility is to use 8.2. But as casts are user
definable, you can add back any casts you want.
On Monday 11 February 2008 14:49, Jeff Davis wrote:
On Mon, 2008-02-11 at 09:09 +0100, Peter Eisentraut wrote:
Ken Johanson wrote:
Is there anything now, or in the works, for compatibility emulation?
For example to setup my session to act like 8.2 and allow less-strict
typing.
The
I noticed that, in one of the third-party databases I have installed
on my server, one foreign key constraint could not be implemented.
(The key columns are of incompatible types.) In previous upgrades I
had seen a warning concerning this constraint, and had passed this
information along
On Feb 10, 2008, at 10:44 AM, Dave Livesay wrote:
I noticed that, in one of the third-party databases I have
installed on my server, one foreign key constraint could not be
implemented. (The key columns are of incompatible types.) In
previous upgrades I had seen a warning concerning this
I acknowledge that from time to time we must accept changes in the 3rd
party software that will break our apps if we (or customers) ever
upgrade them (a compounded issue if we have heavily-used deployments in
the field and not just in-house ones to maintain).
But given the recent and dramatic
Ken,
* Ken Johanson ([EMAIL PROTECTED]) wrote:
But given the recent and dramatic example of 8.3's on-by-default stricter
typing in functions (now not-autocasting), I worry that kind of change
could happen in every minor version (8.4 etc).
8.3 isn't a minor version.
Enjoy,
Stephen Frost wrote:
* Ken Johanson ([EMAIL PROTECTED]) wrote:
But given the recent and dramatic example of 8.3's on-by-default stricter
typing in functions (now not-autocasting), I worry that kind of change
could happen in every minor version (8.4 etc).
8.3 isn't a minor version.
PG
Ken Johanson wrote:
Stephen Frost wrote:
* Ken Johanson ([EMAIL PROTECTED]) wrote:
But given the recent and dramatic example of 8.3's on-by-default
stricter typing in functions (now not-autocasting), I worry that kind
of change could happen in every minor version (8.4 etc).
8.3 isn't a
Magnus Hagander wrote:
PG uses a different versioning system than this one?:
http://en.wikipedia.org/wiki/Software_versioning#Numeric
Or do you mean the changes are not minor? :-)
Yes, we use the one stated on our site, not wikipedia ;)
See: http://www.postgresql.org/support/versioning
Ken Johanson [EMAIL PROTECTED] writes:
Is there anything now, or in the works, for compatibility emulation?
Sure: keep using the same major release. This is one of the reasons
that we keep updating back release branches for so long.
regards, tom lane
On Sat, Feb 09, 2008 at 10:54:38AM -0700, Ken Johanson wrote:
Magnus Hagander wrote:
PG uses a different versioning system than this one?:
http://en.wikipedia.org/wiki/Software_versioning#Numeric
Or do you mean the changes are not minor? :-)
Yes, we use the one stated on our site, not
Ken Johanson wrote:
Magnus Hagander wrote:
PG uses a different versioning system than this one?:
http://en.wikipedia.org/wiki/Software_versioning#Numeric
Or do you mean the changes are not minor? :-)
Yes, we use the one stated on our site, not wikipedia ;)
See:
On Sat, 09 Feb 2008 10:20:51 -0700
Ken Johanson [EMAIL PROTECTED] wrote:
I acknowledge that from time to time we must accept changes in the
3rd party software that will break our apps if we (or customers) ever
upgrade them (a compounded issue if we have heavily-used deployments
in the field
15 matches
Mail list logo
