1 person found this helpful
Thanks for reporting this behavior and researching past forum posts. Actually I see Product Management logged a bug for a similar issue already:
Bug 17740406 - SQL HISTORY TIMESTAMP NOT SORTED AS DATE FOR NON-US LOCALES
At a minimum, there does seem to be some difference involving locale/date formatting between reading and writing the xml.
SQL Developer Team
Is possible that it may be a "Locale" related issue, but I don't know where is the Locale value comming from, since my Windows and SQLDeveloper are in English. See screenshot... http://img822.imageshack.us/img822/5097/6jbq.jpg
Nevertheless, is true that I'm located in Spain, and in previous versions of SQL Developer, the IDE was in Spanish by default, and I had to edit the sqldeveloper.conf file, adding the following option (I like my tools in English)
SQL Developer 4 is correctly showing in English without editing the file.
I see another thread on the subject:
But can't seem to post to that one.
Is there an ETA on when this patch will be made available and and will the patch fix the mess? What's strange is all the XML files appear to have the same timestamp syntax, so this is a mystery. I'm guessing there is an index somewhere and the key is hooped.
No public ETA on a patch, but there will be one.
Are we expecting a patch soon?
You'll hear about it here first.
Check the announcements - the patch has been here for awhile now.
Ok, so you forgot to mention it here...
There's a few dozen threads. We mentioned it in the forum announcements. Sorry you didn't see it, but it's only been out since Feb 25th.
Still no luck with 126.96.36.199...
This bug is closed. If you're seeing something amiss in 4.0.1, you need to start a new thread and post exactly what you're seeing.