completeamateur Posted July 24, 2008 Share Posted July 24, 2008 Hello, I'm looking to optimise the structure of the database behind my website, www.footieclassics.com. There are 25 potential options for each shirt, e.g. an '96 England Shirt' can be purchased in a 'Medium', in 'Excellent' condition. I am looking for a way to structure the database to avoid repeated data. Any ideas? [Products] | +--[National Teams] | | | +--[Argentina] | +--[brazil] | +--[England] | | | +--[96 England Shirt] | +--[04 England Shirt] | +--[06 England Shirt] | | | +--[small] | +--[Medium] | +--[Large] | +--[X-Large] | +--[XX-Large] | | | +--[Excellent] | +--[Good] | +--[Average] | +--[Poor] | +--[Very Poor] | +--[Premiership] +--[Championship] Quote Link to comment Share on other sites More sharing options...
JonnoTheDev Posted July 28, 2008 Share Posted July 28, 2008 I would validate you URL parameters before touching your database. look what happens here: http://www.footieclassics.com/catalogue/index.php?club=hjghghg# Quote Link to comment Share on other sites More sharing options...
completeamateur Posted July 31, 2008 Author Share Posted July 31, 2008 Got to admit, that isn't too pretty! I don't think it's too important though, I would rather optimise the database first. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.