Hi Tom, You are right, I´ve discovered that the to_date was changed to return a timestamp, the original function is returning the right values.
The to_date I´ve found: CREATE OR REPLACE FUNCTION PUBLIC.TO_DATE(text, text) RETURNS TIMESTAMP AS ' BEGIN RETURN pg_Catalog.TO_TIMESTAMP($1,$2); END; ' language 'plpgsql'; I don´t know why they have changed it but anyway why is this changed function returning 01:00:00 in the hour field only for the date 15/10/2006 (DD/MM/YYYY)? It started happening in the first day when Linux has changed to the day light time (15/10/2006). Thanks in advance! Carlos > -----Mensagem original----- > De: Tom Lane [mailto:[EMAIL PROTECTED] > Enviada em: segunda-feira, 16 de outubro de 2006 16:27 > Para: [EMAIL PROTECTED] > Cc: Andreas Kretschmer; Pgsql-General@Postgresql.Org > Assunto: Re: RES: [GENERAL] Dates rejected > > > "Carlos H. Reimer" <[EMAIL PROTECTED]> writes: > > select to_date('16/10/2006','DD/MM/YYYY'); > > to_date > > --------------------- > > 2006-10-16 00:00:00 > > (1 row) > > Um... what have you done to to_date()? The standard version returns a > date, not a timestamp: > > regression=# select to_date('15/10/2006','DD/MM/YYYY'); > to_date > ------------ > 2006-10-15 > (1 row) > > > regards, tom lane > > ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
