From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Subject: | Re: roundoff problem in time datatype |
Date: | 2005-10-13 21:19:01 |
Message-ID: | 200510131419.01729.josh@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Tom,
> I think my preference is to allow '24:00:00' (but not anything larger)
> as a valid input value of the time datatypes. This for two reasons:
> * existing dump files may contain such values
> * it's consistent with allowing, eg, '12:13:60', which we
> allow even though it's certainly not a valid leap second.
It's also consistent with how several other RDBMSes do things (SQL Server,
MySQL), and several programming languages.
--
--Josh
Josh Berkus
Aglio Database Solutions
San Francisco
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Grittner | 2005-10-13 22:39:32 | Re: A costing analysis tool |
Previous Message | Bruce Momjian | 2005-10-13 21:14:55 | Re: [HACKERS] Kerberos brokenness and oops question in 8.1beta2 |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2005-10-13 22:47:10 | Re: [HACKERS] Kerberos brokenness and oops question in 8.1beta2 |
Previous Message | Bruce Momjian | 2005-10-13 21:16:22 | Re: [HACKERS] Kerberos brokenness and oops question in 8.1beta2 |