News for hackers. Stuff that matters.
Re:Unstructured Datatypes in Postgres – Hstore vs. JSON vs. ... by aidos on Thursday July 21, 2016 @08:05AM (#12136247)
One thing you'll run into is that json doesn't have a datetime type so you're left with using either a number of seconds since 1970 (fairly standard) or a string representation [1].

With either approach you'll have to do some mapping in and out of the system (though date probably serialises to string more or less out of the box for most json libs).

[1] http://stackoverflow.com/questions/10286204/the-right-json-d...

Re:Unstructured Datatypes in Postgres – Hstore vs. JSON vs. ... by darklajid on Thursday July 21, 2016 @10:34AM (#12137096)
I mentioned the limitation ("no datetime in json") in my post :-)

That said, you and IanCal have a point: I could just drop the idea of DateTimes and use timestamps/integers - converting queries in my application.

Re:Unstructured Datatypes in Postgres – Hstore vs. JSON vs. ... by aidos on Thursday July 21, 2016 @06:35PM (#12140524)
Ah, yeah, sorry about that... I don't think I'd had my coffee!