From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Kris Jurka <books(at)ejurka(dot)com> |
Cc: | Oliver Siegmar <o(dot)siegmar(at)vitrado(dot)de>, pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: Problems with infinity |
Date: | 2005-01-14 15:38:58 |
Message-ID: | 23736.1105717138@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Kris Jurka <books(at)ejurka(dot)com> writes:
> This looks alright for timestamp, but I don't think this is the right
> thing to do for date and time. The result of getDate should have no hour,
> minute, and seconds component. Likewise for getTime the date components
> should be set to the unix zero epoch. This means that setDate and setTime
> can't really take infinite values (at least how you're proposing), but
> that's not a real issue because pg's date and time types don't support
> infinity. Do you think it is important to support these or is timestamp
> alone enough?
There is a TODO item to allow +infinity and -infinity in the DATE datatype.
So I'd recommend making sure you handle that case, even if it can't
occur today.
Don't recall anyone having ever asked for infinity in the TIME type.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | j.random.programmer | 2005-01-14 16:13:04 | Weird behavior in transaction handling (Possible bug ?) -- commit fails silently |
Previous Message | Oliver Siegmar | 2005-01-14 14:39:48 | Re: Problems with infinity |