Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.databases.ms-sqlserver > #1692

Re: Is it really any point to have a relation in this example

Show all headers | View raw

On Wed, 19 Feb 2014 14:53:51 +0100, "Tony Johansson"
<johansson.andersson@telia.com> wrote:

>Assume that we have many products for example flowers but we have only one 
>warehounse where we plant and store
>these flowers.

     This can be read as one warehouse in total and one for each type.
If the former, you might not need a warehouse column.

>So one Inventory has many flowers but one flower can only exist in one 
>warehouse.
>
>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.

  1) It makes the validation not be hard-coded.  If you add another
warehouse, you can just insert to the table.

  2) You can add warehouse columns, and I would be unlikely to create
a table with just a PK.  I would, at least, have a description.  As
time goes on, you might decide that there are other things about the
warehouse that you wish to track.

Sincerely,

Gene Wirchenko

Back to comp.databases.ms-sqlserver | Previous | Next — Previous in thread | Find similar

Thread

Is it really any point to have a relation in this example "Tony Johansson" <johansson.andersson@telia.com> - 2014-02-19 14:53 +0100
  Re: Is it really any point to have a relation in this example Erland Sommarskog <esquel@sommarskog.se> - 2014-02-19 21:13 +0100
    Re: Is it really any point to have a relation in this example rja.carnegie@gmail.com - 2014-02-19 13:43 -0800
  Re: Is it really any point to have a relation in this example Gene Wirchenko <genew@telus.net> - 2014-02-20 09:49 -0800

csiph-web