"Note: ISO 8601 specifies the use of uppercase letter T to separate the date and time.PostgreSQL accepts that format on input, but on output it uses a space rather than T, as shown above. This is for readability and for consistency with RFC 3339 as well as some other database systems."
So I looked up RFC 3339 (http://www.ietf.org/rfc/rfc3339.txt) and read: "NOTE: ISO 8601 defines date and time separated by "T". Applications using this syntax may choose, for the sake of readability, to specify a full-date and full-time separated by (say) a space character."
Doesn't seem like including the 'T' separator would be inconsistent with RFC 3399?
I'm sending the output of to_json(now()) to web browsers. Most browsers aren't able to parse the date strings if they are missing the 'T' separator. If datetime strings could include the 'T' time separator and the full timezone, that would make generating json that worked with web browsers much simpler.
I'm working with javascript/json systems that expect the 'T' to be there however, so there's no mutual agreement happening.
Thoughts? I know I can hack around it by specifying my own date format, but I'd really like to be able to use row_to_json and other functions without specifying custom date formats everywhere.
