"Matthias" <matthias.ce...@gmail.com> wrote: > It is about when using a upper-boundary timestamp. The value of > 9999-12-31 23:59:59.999999 is sometimes used to indicate an infinite > validity. One other thought -- using a "magic value" for something like this is usually a bad idea. NULL indicates the absence of a value, and means "unknown or not applicable". I generally use that for an upper bound when there is no valid upper bound. In particular, expiration or end dates which will probably eventually be fixed, but haven't been yet, are more appropriately NULL. It isn't that there won't be one; it just isn't known yet -- which fits the semantics of NULL very well. -Kevin
-- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
