David Patte ₯ <dpatte@relativedata.com> writes:
But I believe the primary concern many of us have is that the data provided by the database has been changed unnecessarily, forcing rework and re-interpretation for those that use the database was other than assumed by the maintainers. In many cases this will mean using data from other sources, when the data could easily have been mantained in a single location.
Many people have asked repeatedly for a specific example of a problem, any problem, that occurred or would occur in a real-world program due to these changes. Those requests have been to no avail; all that people have posted in return are opinions, theoretical discussions, and misunderstandings of the database or its maintenance practices. It sounds like you have a concrete example at your fingertips, so please enlighten us about the details! In particular, what would be extremely useful is a specific case involving real-world code where one of the changes in 2013e caused or will cause an actual program to break or misbehave. Please include the specific use case, why the program was using that tzid, what the program did prior to the data change, what the program did after the data change, and why you believe the new behavior is incorrect. And please describe exactly what change to code (rework) you had to do or believe you have to do in order to remedy this problem. Contentless assertions that this has happened or will happen are neither useful nor actionable. Real-world test cases are both, and are considerably more persuasive. -- Russ Allbery (rra@stanford.edu) <http://www.eyrie.org/~eagle/>