From: | Sue Fitt <sue(at)inf(dot)ed(dot)ac(dot)uk> |
---|---|
To: | Chris <dmagick(at)gmail(dot)com> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: setting up foreign keys |
Date: | 2006-08-10 09:20:45 |
Message-ID: | 44DAFA6D.4070606@inf.ed.ac.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Well they don't necessarily have the same value!
It's a dictionary with cross-referenced words, e.g. 'bring' and
'brought' are both headwords in the dictionary, but 'brought' is
cross-referenced to 'bring'. So, the table stores the information (using
integer id's rather than words) that
bring: bring
brought: see bring
sing: sing
sang: see sing
etc.
Sue
Chris wrote:
> Sue Fitt wrote:
>> Thanks Chris and Chris, you've solved it.
>>
>> I had a gui open that connects to the database. It was doing nothing
>> (and not preventing me adding to or altering headwords_core via
>> psql), but having closed it the table is instantly created. Weird.
>>
>> BTW, referencing the same column twice is deliberate, it's a
>> cross-reference.
>
> The same column and the same table?
>
> Same column different table I could understand but not the same column
> & table ;)
>
> I'm sure there's a reason for it though :)
>
From | Date | Subject | |
---|---|---|---|
Next Message | Richard Huxton | 2006-08-10 09:23:55 | Re: Beginner optimization questions, esp. regarding Tsearch2 |
Previous Message | Chris | 2006-08-10 09:13:29 | Re: setting up foreign keys |