This week's book giveaway is in the Agile and other Processes forum. We're giving away four copies of The Mikado Method and have Ola Ellnestam and Daniel Brolund on-line! See this thread for details.
Is it possible to design a database with tables within tables? For instance: The Big Moose Saloon can be one table consisting of all the forums which each can be one table consisting of all the queries which in turn each can be a table consisting of all the replies.
So in summation it looks like this: BigMooseSalon--->Individual Forums---->Individual Queries--->Replies. So BigMooseSaloon is a table consisting of all the individual forums which each is a table consisting of all the individual queries which in turn can be its own table that consists of all the replies. So getting back to my original question, can you design a database like this, using tables within tables? And if so, is it a good idea or bad idea?
Thanks for any input.
- Sean
Daniel Dunleavy
Ranch Hand
Joined: Mar 13, 2001
Posts: 276
posted
0
You can do it but the downside is it may make sql statement down the line more difficult as your system becomes bigger. Its easier to modify a simple design than a complex one. Dan
Sean Casey
Ranch Hand
Joined: Dec 16, 2000
Posts: 625
posted
0
Yeah, I figured that out on my own. Instead I took some time to design the database and used foreign keys. Thanks for your reply though.
I agree. Here's the link: http://ej-technologies/jprofiler - if it wasn't for jprofiler, we would need to
run our stuff on 16 servers instead of 3.