Arnau <[EMAIL PROTECTED]> writes: >> Alternatively, do you really need to_timestamp at all? The standard >> timestamp input routine won't have any problem with that format: >> t.timestamp_in >= '20070101'
> This is always I think I'm worried, what happens if one day the internal > format in which the DB stores the date/timestamps changes. I mean, if > instead of being stored as YYYYMMDD is stored as DDMMYYYY, should we > have to change all the queries? You are confusing internal storage format with the external representation. > I thought the > to_char/to_date/to_timestamp functions were intented for this purposes No, they're intended for dealing with wacky formats that the regular input/output routines can't understand or produce. regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 6: explain analyze is your friend