Re: Multiple Columns Keys - Good or Bad idea?

From: Rob Brown-Bayliss <rob(at)ZOOstation(dot)cc>
To: PGSQL Novice List <pgsql-novice(at)postgresql(dot)org>
Subject: Re: Multiple Columns Keys - Good or Bad idea?
Date: 2001-06-13 03:43:25
Message-ID: 992403805.27623.0.camel@ZOOstation.cc
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-novice

> I'd go for the first method. If you need to refer to the integrated table
> often (e.g. as foreign key in other tables), it may be a good idea to give it
> a new sequence. So the integrated table will have location, the sequence
> number at the remote site, and a unique local sequence number.

Thanks folks,

I have decided to mix and match, I have changed the primary key to a
text field and created a function that merges the location ID and the
sequence like '46-153453'

So I can still get the data from specific sites if needed and have only
one key...

--

Rob Brown-Bayliss
---======o======---
www.ZOOstation.cc

In response to

Browse pgsql-novice by date

  From Date Subject
Next Message Ryan Ho 2001-06-13 05:18:54 Optimizing complex queries
Previous Message Tom Lane 2001-06-12 20:02:57 Re: AW: FATAL ERROR