Subject | Re: [Firebird-Architect] View updates and upward compatibility |
---|---|
Author | Fabricio Araujo |
Post date | 2004-10-29T03:25:21Z |
On Tue, 19 Oct 2004 09:37:04 -0400, Jim Starkey wrote:
If it is not documented, don't bother to "keep compatibility".
It's maintenance only creates new trouble and create more
traffic for support lists (as if it is not enoughly crowded).
For me, rip it off.
>>In our short FB history, controversial changes have been discussed andThousands? Jim, this behavior is not ever documented!!!!
>>tested in the list. Incompatible changes with previous versions (where the
>>old versions were considered at fault) were done after general agreement.
>>It's almost impossible that "general" equals "unanimous".
>>
>So, you are arguing that a single keyword on future view definitions is
>too hgih a price to pay to keep thousands of existing production systems
>working? Or are you arguing that an implicit decision once made cannot
>be reviewed?
If it is not documented, don't bother to "keep compatibility".
It's maintenance only creates new trouble and create more
traffic for support lists (as if it is not enoughly crowded).
For me, rip it off.