<soapbox> How can you guys advise normalization if you don't know what the entire database looks like and what relations there are? I find it silly to send people to look for sites that talk about normalization without understanding what they deal with.
There are people who take it to the 4th normal form and beyond, not because it's more efficient, but because they can. I call that the stupid level, because in the name of normalization, one introduces complexity and processing overhead. </soapbox> Gerry On 7/15/06, Duane A. Couchot-Vore <[EMAIL PROTECTED]> wrote: > --- In [email protected], Pete <[EMAIL PROTECTED]> wrote: > > > Your database is not designed correctly. > > > > The items should be in one table, the prices in another. That way, > > there are no problems for you. > > I'd like to second this. Even though it might be working how, you > could run into big headaches down the road. Google "database > normalization" and reconsider how you have it set up. ------------------------ Yahoo! Groups Sponsor --------------------~--> See what's inside the new Yahoo! Groups email. http://us.click.yahoo.com/2pRQfA/bOaOAA/yQLSAA/CefplB/TM --------------------------------------------------------------------~-> The php_mysql group is dedicated to learn more about the PHP/MySQL web database possibilities through group learning. Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/php_mysql/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
