In article <Vqgxe.134972$Ql.7257205_at_phobos.telenet-ops.be>,
jan.hidders_at_REMOVETHIS.pandora.be says...
> Like I said, as a special value. Another option is to treat the field as
> a set-valued field (since it apparently can contain 0 or 1 values) which
> means that you are not in 1NF and should first normalize such that you are.
In theory, set-valued fields definitely do not violate 1NF. They may
still be a bad design choice, though, and anyway I guess the point in
this thread is to give practical advice for implementation in SQL
databases without proper domain support. So you should normalise. :)
--
Jon
Received on Sat Jul 02 2005 - 04:34:24 CDT
