[ https://issues.apache.org/jira/browse/FLEX-24411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Justin Mclean updated FLEX-24411: --------------------------------- Labels: easyfix (was: ) > DateFormatter.parseDateString() function doesn't properly read in SQLite > seconds values > --------------------------------------------------------------------------------------- > > Key: FLEX-24411 > URL: https://issues.apache.org/jira/browse/FLEX-24411 > Project: Apache Flex > Issue Type: Bug > Components: Formatters > Affects Versions: Adobe Flex SDK 3.5 (Release) > Environment: Affected OS(s): All OS Platforms > Affected OS(s): All OS Platforms > Browser: Firefox 3.x > Language Found: English > Reporter: Adobe JIRA > Labels: easyfix > > Steps to reproduce: > 1. Create a date object using the dateFormatter and the default date format > (according to http://www.sqlite.org/datatype3.html). Use a set of code > something like this: > var dateObj:Date = DateFormatter.parseDateString("2010-07-02 12:36:18.000"); > > Actual Results: > The date object created has a seconds value of 0. > > Expected Results: > The date object created should have a seconds value of 18. > > Workaround (if any): > Ensure that you store date strings into your SQLite databases in a the format > of "YYYY-MM-DD HH:NN:SS" without the milliseconds value at the end of it. > Notes: > This problem also exists in 3.6.x. I think that certain older versions of > the Flex/Air SDK didn't store the milliseconds values on dates when writing > into SQLite databases by default because I hadn't encountered this problem > until I upgraded my application to use the 1.5.3 AIR SDK. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira