>> Taking just the weblog example, what I mean is for each weblog to have >> its own set of numeric IDs for posts independent of any other weblog's >> data that is in the same installation of the app even though all the >> post data is in the same table. Everybody's data should be in the same >> set of tables though to allow various aggregate queries. > > Unless I was taught wrong, you should really just split it up into two > tables with a one-to-many relationship. However, if you're trying to hack > a pre-made application and there's no other way to get around it, you can > do the double-unique-id-in-the-same-table method, but it gets messy.
Hold on, I just re-read the thread. Maybe I am getting this wrong. Are you trying to do this: Weblogs ------- 1: Joe's blog 2: Jane's blog 3: John's blog Entries ------- 1: weblog->1: Joe's first entry 2: weblog->1: Joe's second entry 1: weblog->2: Jane's first entry 2: weblog->2: Jane's second entry Sorry for getting everything mixed up! :) --- Joe Topjian email: [EMAIL PROTECTED] web: http://joe.terrarum.net
