On mån, 2012-05-21 at 15:34 +1000, Brendan Jurd wrote:
I'd be okay with just adding a note in the manual under Date/Time
Output to the effect of Note: ISO 8601 specifies the use of uppercase
letter 'T' to separate the date and time. Postgres uses a space for
improved readability, in line with
Peter Eisentraut pete...@gmx.net writes:
On mån, 2012-05-21 at 15:34 +1000, Brendan Jurd wrote:
I'd be okay with just adding a note in the manual under Date/Time
Output to the effect of Note: ISO 8601 specifies the use of uppercase
letter 'T' to separate the date and time. Postgres uses a
On 24 May 2012 05:30, Peter Eisentraut pete...@gmx.net wrote:
On mån, 2012-05-21 at 15:34 +1000, Brendan Jurd wrote:
I'd be okay with just adding a note in the manual under Date/Time
Output to the effect of Note: ISO 8601 specifies the use of uppercase
letter 'T' to separate the date and time.
Brendan Jurd dire...@gmail.com writes:
I'd be okay with just adding a note in the manual under Date/Time
Output to the effect of Note: ISO 8601 specifies the use of uppercase
letter 'T' to separate the date and time. Postgres uses a space for
improved readability, in line with other database
On lör, 2012-05-19 at 11:52 -0400, Daniel Farina wrote:
The documentation is misleading to the point of our support for ISO
8601-strict parsing.
http://archives.postgresql.org/pgsql-hackers/2012-02/msg01237.php
A very fine point, but I discovered it not out of curiosity, but a
fairly
Peter Eisentraut pete...@gmx.net writes:
The problem is that people think that ISO means ISO 8601, whereas it
actually means ISO 9075. I can see how that's an easy mistake to make,
though.
... especially since we keep referring to 8601 in our own docs.
Does this mean we should do a global
On 22 May 2012 02:58, Tom Lane t...@sss.pgh.pa.us wrote:
Peter Eisentraut pete...@gmx.net writes:
The problem is that people think that ISO means ISO 8601, whereas it
actually means ISO 9075. I can see how that's an easy mistake to make,
though.
... especially since we keep referring to
On 20 May 2012 01:52, Daniel Farina dan...@heroku.com wrote:
The documentation is misleading to the point of our support for ISO
8601-strict parsing.
http://archives.postgresql.org/pgsql-hackers/2012-02/msg01237.php
A very fine point, but I discovered it not out of curiosity, but a
fairly
On Sun, May 20, 2012 at 10:34 PM, Brendan Jurd dire...@gmail.com wrote:
What we don't do is *output* the 'T', but this is pretty easy to
workaround, e.g., to_char(now(), '-MM-DDTHH24:MI:SS'). The
scope of actually wanting the 'T' is surely pretty minor?
I'd be okay with just adding a
On Sat, May 12, 2012 at 5:37 AM, Simon Riggs si...@2ndquadrant.com wrote:
Do we have a full list of externally defined open standards that we follow?
Are there any known incompatibilities from externally defined open standards?
(I know about the SQL standard stuff).
The documentation is
Do we have a full list of externally defined open standards that we follow?
Are there any known incompatibilities from externally defined open standards?
(I know about the SQL standard stuff).
Are there any things that need standards that don't have them? (Be brief)
Some high level general
On lör, 2012-05-12 at 10:37 +0100, Simon Riggs wrote:
Do we have a full list of externally defined open standards that we
follow?
Well, there are a lot of them, starting with things like ASCII and ANSI
C.
If you grep through the documentation for things like RFC or ISO,
you will find a number
12 matches
Mail list logo
