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 --------------------------------------------------------------------- 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
