"John D. Burger" <[EMAIL PROTECTED]> writes:
> Hmm, except if the timestamp "anchor" is installation-specific, then
> binary exchange of timestamps is complicated.
Yeah, that would be a problem.
> What does libpq do now
> with timetamps, if the client requests data in binary form? How does
Note: When timestamp values are stored as double precision
floating-point numbers (currently the default), the effective limit of
precision may be less than 6. timestamp values are stored as seconds
before or after midnight 2000-01-01. Microsecond precision is achieved
for dates within a few year
=?ISO-8859-1?Q?St=E9phane_Schildknecht?= <[EMAIL PROTECTED]> writes:
> In fact, I wonder why a date ranging from somme 4000 BC to 3 AC is
> stored as a reference to the 1st january of 2000. Is it because that day
> is some "close to actual time" date ?
The restriction to 4713BC comes from the
Stephan Szabo wrote:
On Thu, 3 Jun 2004, Jeff Boes wrote:
(asked last week on .questions, no response)
Can anyone explain why this happens? (under 7.4.1)
select '2004-05-27 09:00:00.51-04' :: timestamp(0) ;
timestamp
-
2004-05-27 09:00:01
select '20
