jcesare
Well-known member
planet4ever said:I had a crazy thought as I was falling asleep last night. What if some idiot setting up the order database made the order date field type character instead of numeric or date? And what if dates are getting entered there in month/day/year format? Things would have worked pretty smoothly so long as Aug and Sep order dates were entered as '08/31/2010' and '09/xx/2010', but pity anyone whose date was entered as '9/xx/2010'. The records for those poor souls would sort as ordering later than the '10/xx/2010' folks.Bassman said:I ordered in September and am getting my LEAF the same timeframe as people who ordered 4 months later?
Or, rather, I should say things would have worked relatively smoothly until people started ordering in '01/xx/2011'. Those people would immediately show up as having the "earliest" dates for which the car had not yet started the manufacture process. Even if the date was entered as '1/xx/2011' they would be "older" than everyone except the '08/31' and '09/xx' folks. ('/' is lower in the ANSi collating sequence than '0'.)
I know, only a retired programmer's laughable nightmare, but it sure would explain why no one can make sense of the delivery sequence.
Ray
Nice theory but the Japanese localization for a date format is yyyy-mm-dd. Our order data would have been entered in a database in Japan, and since there is a difference in Euorpean and US localization, I'm sure they used a date time data type, not a string. It is possible that they screwed up importing US dates and European dates into their database.