MySQL Forums
Forum List  »  Connector/Node.js

Re: XML output format
Posted by: Nick Bishop
Date: December 01, 2006 03:49PM

This type of change makes it difficult for developers to "future proof" their code.

I think there is a wrong way and a right way of making these types of changes. The right way of making this change would have been to commission a new option like

--xml-50 (and to take account of the even newer format in 5.0.26: --xml-5026)

and leave the old --xml option to produce the old format.

My complaint is that when developers write an application revolving around the then-current version (3.x), they have no way of knowing any of the possible, future changes of output format from using --xml (or any other output format).

While it is possible to keep running 3.x forever, it is not a reasonable solution. Organisations upgrade either as a security precaution, or to gain access to a specific functionality/ies. They do not want to scan screeds of release notes, and then to scan pages of (non-existent?) source code for any required changes.

Obviously, only a small proportion of changes are like this, but we do have to be careful.

Options: ReplyQuote

Written By
January 10, 2006 12:09PM
January 10, 2006 06:23PM
January 11, 2006 10:16AM
Re: XML output format
December 01, 2006 03:49PM
January 11, 2006 10:56AM
January 13, 2006 06:34PM

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.