Hello, With a decent database design, you won't need as many tables. Let me try:
Tables for each basic object: (1) One table for stellar objects (2) One table for user "comments" (3) One table for ratings (4) One table for "conjunctions" (5) One table for users Link tables: One table to link them all: some USER gives a COMMENT about a STELLAR OBJECT in a particular CONJUNCTION or a RATING about such a comment, along with a comment about the comment, or the rating :) Maybe this is a bit too easy, but it shows that there are ways not to end up with hundreds of tables. Your "link table" will have many thousand rows, but you can optimise that by using some more tables to have better "link granularity". Anyway, we have just transformed a great number of tables into a great number of rows... ;) -----Message d'origine----- De : Thomas Spahni [mailto:[EMAIL PROTECTED]] Envoye : lundi 8 juillet 2002 10:30 A : Ben Ocean Cc : [EMAIL PROTECTED] Objet : Re: Deep Nesting Ben, The description of your project is as clear as mud or as clear as astrology in general, but it seems to me that you could put all data into one table? However, a bigger number of tables is no problem for MySQL. Using MyIsam tables each table will be equivalent to 3 files. With ReiserFS you should be able to create 100000 of them without running into trouble. Don't try this with ext2. Thomas On Sun, 7 Jul 2002, Ben Ocean wrote: > Hi; > I'm trying to programmatically create tables which are nested so deeply > that I fear I'll be creating a gargantuan number of them. I'm seeking a > means to limit this, if possible. I'm creating what I call *open source > metaphysics*. Here's the scenario: > > The tables will be used to enable users to enter comments concerning what > they believe happens at individual conjunctions. For example, in astrology, > let's say one enters a comment of what happens when the Moon enters > Scorpio. These comments can then be called by other users and rated with an > accreditation system similar to Amazon's rating of books (and those who > rate them). > > The problem occurs with granulation. Let's say, instead, that our above > example is when the Moon enters Scorpio while the Sun is in the fifth > degree of Aries and Mars is in the twentieth degree of Gemini while the > natal chart reflects that this nativity has an ascendant at the seventh > degree of Cancer, etc. Indeed, it's actually far more involved than that, > because I'd like to cross-reference other metaphysical systems (Tzolkin, I > Ching, etc.) several of which have nativities as well as transient > elements. I can see tables literally in the thousands (or much higher) with > no way to avoid this proliferation. Any suggestions? > > TIA, > BenO > > sql, query --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
