Search Postgresql Archives

Re: 2 versions of an entity worth distinct table?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



But then a) because you can't guarantee this design won't 'improve' and b) you would like to look in one place for all addresses, normalize now.

Thomas Kellerer wrote:
gvim wrote on 27.12.2010 02:47:
If a table representing contact details can have 2 but no more than 2
email addresses is it really worth factoring-out email addresses to a
separate table.

If you are absolutely sure you will never have more than two, then I agree, you don't need to create a 1:N relationship for that. Especially because guaranteeing that there will never be more than two in the N part is quite complicated.

Regards
Thomas



--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux