Joins and links

From: "Ansley, Michael" <Michael(dot)Ansley(at)intec(dot)co(dot)za>
To: "'pgsql-general(at)postgreslq(dot)org'" <pgsql-general(at)postgresql(dot)org>
Subject: Joins and links
Date: 1999-07-06 07:19:21
Message-ID: 1BF7C7482189D211B03F00805F8527F70ECFF8@S-NATH-EXCH2
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

>> Hmm a very interesing theoretical topic...
>> Wouldnt make sense to tie this in with the implementation of a Foriegn
Key?
>> So when the foriegn key is defined you create anoter index that stores
all
>> the relevant child to parent relationships and can be used to speed up
that
>> access since it obviously will be a primary access route (else thay
wouldnt
>> have defined it). I would think it could be used then to check the
Foreign
>> Key integrity and used to help maintain/construct clustered tables...
I read about this recently in a warehousing (again, sic) magazine, and I
think
it's a great idea. I think that in certain areas, the performance benefits
would
make it well worth while, although obviously you have to be careful in
design. It
simply removes the need for the second scan because the keys are used to
link the
records, and this is managed totally by the dbms.

Sorry about the previous unfinished message. Ctrl-Enter does a send on my
mail client,
now I know.

MikeA.

Browse pgsql-general by date

  From Date Subject
Next Message David Warnock 1999-07-06 08:28:58 Re: Fw: Re[2]: [GENERAL] Joins and links
Previous Message Ansley, Michael 1999-07-06 07:13:47 RE: pgsql-general-digest V1 #376