I want to create a new object, with a start & end date using the standard UI-bootstrap DatePicker.
I will send these date, using Ajax, to my server, where some PHP which I code will store it in a MySql database.
Coming from a PHP background, my first instinct is to store date/time as a Unix timestamp.
Since (Angular) JS has a millisecond resolution and Unix timestamps have a second resolution, that involves multiplying/dividing by 1000.
My server is returning data as a JSON, and I would rather not change that.
Ideally, I would like to do any conversion on the server, since it ought to have more processing power, and just initialze by AngularJS model fronm the JSON received.
Would it be acceptable to store the date as strings in the MySql database, rather than a timestamp? That way the downloaded data could be used unchanged to initialize the DatePicker.
Since I am having trouble getting the DatePicker to show the date which it receives from the server (as Unix timestamp), this seems like the simpler approach, but is there anything to watch out for, if I do so?
How do others do this?