Subject | RE: [Firebird-Architect] Re: View updates and upward compatibility |
---|---|
Author | Leyne, Sean |
Post date | 2004-10-19T18:00:18Z |
Paul,
But what is being overlooked is the fact that production system never
migrate to a new version without review/testing/etc.
Accordingly, the suggestion that it will 'break production systems' is a
misnomer/small-to-medium red herring!
anyways.
Sean
> We have two viewpoints:Agreed.
> - this behaviour is wrong, undocumented, non-standard, used by very
> few app's and a support headache
> - changing this behaviour will break thousands of production systems
But what is being overlooked is the fact that production system never
migrate to a new version without review/testing/etc.
Accordingly, the suggestion that it will 'break production systems' is a
misnomer/small-to-medium red herring!
> I do not have hard numbers, I would assume that the most likely classBut replication tools need to be update to support the new version,
> of app's to break are replication tools.
anyways.
> I am somewhat surprised that Sean's suggestion of some sort ofThanks.
> config/dialect based solution did not get more discussion. Seems a
> sensible approach to me.
Sean