Re: FW: db design - which is better

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

 



There are perhaps such times, but I have yet to meet one.

with 1NF:
- your table space will be smaller
- your indexes will work better
- your SQL will be easier to write
- ease of maintenance

Just my 2 Belgian francs

Ignatius
_________________________
----- Original Message -----
From: "mayo" <mayo@xxxxxxxxxxxxxxxxxx>
To: "php-db" <php-db@xxxxxxxxxxxxx>
Sent: Saturday, February 07, 2004 23:45
Subject: RE:  FW: db design - which is better


>
> Thanks,
>
> There just seems to be times when non-normalized table structures are
easier
> to work with. A few hundred to a few thousand records, maybe 20 fields,
> rarely adding another field.
>
> I wonder sometimes whether it make sense to put everything in one table
> instead of using joins.
>
> yours, putting-his-foot-in-his-mouth,
>
> Gil
>
>
>  > -----Original Message-----
>  > From: Ignatius Reilly [mailto:ignatius.reilly@xxxxxxx]
>  > Sent: Saturday, February 07, 2004 5:33 PM
>  > To: mayo; php-db
>  > Subject: Re:  FW: db design - which is better
>  >
>  >
>  > Use the second design. SQL 101 / 1st normal form.
>  > _________________________
>  > ----- Original Message -----
>  > From: "mayo" <mayo@xxxxxxxxxxxxxxxxxx>
>  > To: "php-db" <php-db@xxxxxxxxxxxxx>
>  > Sent: Saturday, February 07, 2004 23:19
>  > Subject:  FW: db design - which is better
>  >
>  >
>  > >
>  > >
>  > > -----Original Message-----
>  > > From: Gilbert Midonnet [mailto:glm@xxxxxxxxxxxxxx]
>  > > Sent: Saturday, February 07, 2004 5:09 PM
>  > > To: php-db
>  > > Subject: db design - which is better
>  > >
>  > >
>  > > I have a client who has hundreds of articles. Each article can
>  > be seen by
>  > > one or more permission groups.
>  > >
>  > > I have questions regarding setting up the an article_display table.
>  > >
>  > > The easiest table to read and to conceptualize would list the
>  > articles and
>  > > use a boolean for each of the permission groups (let's call the PGs
for
>  > this
>  > > example).
>  > >
>  > > (articleNameID refers back to the article table)
>  > >
>  > > articleNameID---PG1---PG2---PG3---PG4---PG5
>  > > 1001-------------1-----0-----0-----0-----0
>  > > 1002-------------1-----1-----0-----0-----0
>  > > 1003-------------0-----0-----1-----0-----0
>  > >
>  > >
>  > > Or should the table set up be:
>  > >
>  > > articleNameID--PG
>  > > 1001------------1
>  > > 1002------------1
>  > > 1002------------2
>  > > 1003------------3
>  > >
>  > > etc...
>  > >
>  > > gil
>  > >
>  > > --
>  > > PHP Database Mailing List (http://www.php.net/)
>  > > To unsubscribe, visit: http://www.php.net/unsub.php
>  > >
>  > >
>  >
>  > --
>  > PHP Database Mailing List (http://www.php.net/)
>  > To unsubscribe, visit: http://www.php.net/unsub.php
>  >
>
> --
> PHP Database Mailing List (http://www.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

-- 
PHP Database Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php


[Index of Archives]     [PHP Home]     [PHP Users]     [Postgresql Discussion]     [Kernel Newbies]     [Postgresql]     [Yosemite News]

  Powered by Linux