Re: [SQL] Database design - AGAIN

2003-06-25 Thread Josh Berkus
Rudi, > I'll be using smaller tables with appropriate join tables and PHP. > Just for interests sake I'll be using Dia to plan the schema. > I prefer to use the UML drawing tools instead of the ER ones. I still use a simple flowcharting program to plan my databases. Never saw the value in UML

Re: [SQL] Database design - AGAIN

2003-06-24 Thread Michael A Nachbaur
On Tuesday 24 June 2003 03:15 pm, Rudi Starcevic wrote: > I'll be using smaller tables with appropriate join tables and PHP. > Just for interests sake I'll be using Dia to plan the schema. > I prefer to use the UML drawing tools instead of the ER ones. Off topic, but if you're using KDE you might

Re: [SQL] Database design - AGAIN

2003-06-24 Thread Rudi Starcevic
Josh, Jonathan .. Thanks for your replies. You mail was exactly what I was hoping for - your best practise opinion. I do have a grasp of the theory involved with SQL but your input on those 'other' constraints like time, language, longevity etc was just what I was interested in. I'll be using sm

Re: [SQL] Database design - AGAIN

2003-06-24 Thread Jonathan Gardner
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday 23 June 2003 22:19, Rudi Starcevic wrote: > I"m not sure whether to have on larger table or 2 smaller one with a > join table. Theory says you are better off with the join tables. Practical reality agrees with this. It takes a bit more work

Re: [SQL] Database design - AGAIN

2003-06-24 Thread Josh Berkus
Rudi, > For this task, a searchable directory, which design would be better. > In know the second is more flexible as new features can be added but I > have very limited time and > I think the one larger table design would be quicker to build. Sounds like you already have a clear grasp of the sit