Bookmarks

Yahoo Gmail Google Facebook Delicious Twitter Reddit Stumpleupon Myspace Digg

Search queries

www.webdp.net, Event 9 IIS log failed to write entry, wwwxxx jeffs, Catastrophic failure Unexpected method call sequence. 0x8000ffff (-2147418113)., ksh lock a file, [unixODBC][Driver Manager]Driver's SQLAllocHandle on SQL_HANDLE_DBC failed, sed: -e expression #1, char 1: unterminated address regex, procmail + change subject, w2ksp4.exe download, /proc/kallsyms format

Links

XODOX
Impressum

#1: blank columns or separate tables

Posted on 2007-09-07 00:01:17 by Pasquale

I have a form with 8 fields, 4 of which are required and 4 are not.
Usually if a field isn't required I would create a separate table for it
rather than having a blank value in the table where required values
would go. In this case, I'm not sure if I should put all the not
required fields in one table or separate tables. Since any one of them
can be or not be blank.

I'm trying to find a balance between normalization and practicality for
the database, as well as programming.

So, are columns with blank values acceptable to a certain number? Are 4
separate tables too many, so that there aren't any blanks in a column if
they were in one table?

Thanks,
Pasquale

Report this message