Re: [SQL] Bad date representation

From: Herouth Maoz <herouth(at)oumail(dot)openu(dot)ac(dot)il>
To: Roland_DUBOULOZ <Roland(dot)Dubouloz(at)bull(dot)net>, pgsql-sql(at)postgreSQL(dot)org
Subject: Re: [SQL] Bad date representation
Date: 1999-07-11 14:57:33
Message-ID: l03130306b3ae6060caff@[147.233.159.109]
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

At 12:25 +0300 on 09/07/1999, Roland_DUBOULOZ wrote:

> 2.-postmaster -i
>
> insert into FOO values('06-22-1999');
> insert into FOO values('06-07-1999');
> insert into FOO values('23-06-1999'); <---- no ERROR
> WE Have NO ERROR !!!!! why ???
>
> and on select * from FOO the result is
>
> date
> ----------
> 06-22-1999
> 06-07-1999
> 06-23-1999

The way Postgres parses dates is: first, see if there is more than one way
to interpret the date. If there is more than one way, use the DateStyle.

So, if it sees a date like 23-06-1999, there is only one way to interpret
it - that the 23 is the day, and the 06 is the month. In that case, this is
June 23rd, and everything is OK. But a date like 08-06-1999 could be either
August sixth or June eighth. In that case, it uses the DateStyle to
determine which.

This algorithm gives you some lenience.

Herouth

--
Herouth Maoz, Internet developer.
Open University of Israel - Telem project
http://telem.openu.ac.il/~herutma

In response to

Browse pgsql-sql by date

  From Date Subject
Next Message Tom Lane 1999-07-11 15:38:43 Re: [SQL] Re: [HACKERS] SELECT DISTINCT question
Previous Message Herouth Maoz 1999-07-11 14:37:03 Re: [SQL] uncorrelated subqueries