Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Erland Sommarskog Newsgroups: comp.databases.ms-sqlserver Subject: Re: Is it really any point to have a relation in this example Date: Wed, 19 Feb 2014 21:13:33 +0100 Organization: Erland Sommarskog Lines: 18 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit Injection-Info: mx05.eternal-september.org; posting-host="fd3d6d0229f14a752f017d8f9903addd"; logging-data="25890"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+c+RjDBEyuh1Y1ZAGswANZ" User-Agent: Xnews/2006.08.24 Mime-proxy/2.1.c.0 (Win32) Cancel-Lock: sha1:TptH/nig9Ilij0dy+NGhXyCXNBY= Xref: csiph.com comp.databases.ms-sqlserver:1690 Tony Johansson (johansson.andersson@telia.com) writes: > In this example is it any point to create a separate table for warehouse. > Is it just as good to store information such as current quantity for each > flower that exist in the product table. > > I find it funny to have a table warehouse with just an Id without any more > fields. Most likely the warehouse have other attributes like name, address, etc. But even we assume something that only has an ID, which in this case must be a natural key, it should probably be a separate table, as a foreign-key constraint to this table helps to restrict the possible values in the column. -- Erland Sommarskog, Stockholm, esquel@sommarskog.se