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.


Search Discussions

Discussion Posts


Follow ups

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 15 of 29 | next ›
Discussion Overview
grouppgsql-general @
postedJan 21, '13 at 3:26p
activeJan 27, '13 at 11:28a



site design / logo © 2021 Grokbase