id,summary,reporter,owner,description,type,status,priority,component,severity,resolution,keywords,cc,release
8964,Store the date as a timestamp,rjollos,doki_pen,I made the bad assumption that the date was being stored as an integer_ as Trac does for Milestone's `due` and `completed` fields. A problem can occur if you change the `separator` or date `format` after some data has been entered; the database now has different formats for the date in its row. Here is an example:\r\n\r\n[[Image(TracDbTable.png)]]\r\n\r\nThis also makes it more difficult for other plugins to query and do something useful with the data because they need to get the `format` from trac.ini. Storing the value as an integer would also make comparisons possible_ which would help with implementing features such as #6410.\r\n\r\nI'm wondering what led to the design decision to store the field as text. Do you see any downsides to storing it as an integer?\r\n,enhancement,closed,normal,DateFieldPlugin,normal,wontfix,date time storage value,ChrisNelson_ hasienda_ bof_ matobaa,0.11