Hi! >>>>> "Bernt" == Bernt M Johnsen <bernt.john...@sun.com> writes:
>>>>>>>>>>>>> Michael Widenius wrote (2009-01-24 02:07:54): >> As Dmitri pointed out, we shouldn't deprecate '.' as substitute for >> dates. >> >> Another things is that we should stop making decisions about >> incompatible changes without listening to the MySQL users. They know >> more than we how MySQL is used and they are directly affected of any >> incompatible change we force upon them. Bernt> Ok. And what is the users' verdict? Do they want a "helpful" best Bernt> effort interpretation of time and dates or do they want a well-defined Bernt> standardized portable scheme which reduces the possibilities of bugs? Normally they don't want their existing applications to break. Bernt> And what does this "helpfullness" lead to? In Norway it is common to Bernt> write dates as DD.MM.YY. So a buggy program that accepts 01.02.03 (for Bernt> the date 2003-02-01) whould be able to insert it into MySQL without Bernt> errors, but when retrieved the value is 2001-02-03. I don't think the Bernt> user/programmer is happy with that. They will quickly notice this and fix their time order. In reality we haven't got many complains from Norway about this, so I assume they are smart enough in Norway to not run into this problem. Its more important that we don't break things for current users than try to be concerned about possible wrong usage that no one seams to do or find important enough to complain about. Bernt> We have a Norwgeian word for this "helpfullness": "bjørnetjeneste", but Bernt> I'm not sure what the english idiom would be. Regards, Monty -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=arch...@jab.org
