Adrian Klaver wrote: > If I was following Gavan correctly, he wanted to have a single > timestamp field to store calender dates and datetimes. In other > words to cover both date only situations like birthdays and > datetime situations like an appointment. If that is actually true, it sounds like some reading on the benefits of normalizing to 3rd normal form is in order. What you describe is a violation of first normal form. Now, I recognize that most databases of any complexity need to denormalize to one degree or another for performance reasons; but I don't see the benefit of this particular type of denormalization. -Kevin -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
