Re: Quick Question About Dbase Architecture

2007-09-18 Thread Dinner
On 9/18/07, Matt Robertson <[EMAIL PROTECTED]> wrote:... > I suppose if you were a fanatic about data normalization you would create > a > table for 'lookups' and have it contain only ID and ItemType. Then your > lookup table has an indexed ParentID field (foreign key) replacing the > ItemType fi

Re: Quick Question About Dbase Architecture

2007-09-18 Thread Matt Robertson
A single lookup table should work fine for this. I don't see a need to create a different table for each lookup. Field structure ID (int, indexed) ItemType (varchar 25, indexed) ItemStored (char3) ItemDisplay(varchar 25) The field lengths above are not set in stone, and I am assuming your profi

RE: Quick Question About Dbase Architecture

2007-09-18 Thread Brad Wood
is I can rename options, add options, or inactivate options and the entire site updates instantly without any new CF code. ~Brad -Original Message- From: Joel Watson [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 18, 2007 11:08 AM To: CF-Talk Subject: Quick Question About Dbase

RE: Quick Question About Dbase Architecture

2007-09-18 Thread Dave Watts
> For improved performance you could build views that join the > tables together. Views are faster than running plain old > select queries and doing all the joins. This is not generally true, actually. To improve performance, views have to be indexed or materialized, and they generally aren't b

Re: Quick Question About Dbase Architecture

2007-09-18 Thread Joel Watson
>Joel, > >if you want to have your database relational to 3rd normal form then yes you >should have separate tables for all of your lookups. Databases are designed >to work well with joins of that nature and if you build your indexes >correctly you should be ok. A lot of people forget to add inde

Re: Quick Question About Dbase Architecture

2007-09-18 Thread gary gilbert
Joel, if you want to have your database relational to 3rd normal form then yes you should have separate tables for all of your lookups. Databases are designed to work well with joins of that nature and if you build your indexes correctly you should be ok. A lot of people forget to add indexes on

Quick Question About Dbase Architecture

2007-09-18 Thread Joel Watson
I have a profile form that has about 7 drop-down menus (marital status, education level, etc.), all required fields. How do most handle this? Do you create a separate table for each collection and then have foreign keys on the "profile" table, or do you simply pass in literal values to the d