| From: | Gavin Flower <GavinFlower(at)archidevsys(dot)co(dot)nz> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: ID column naming convention |
| Date: | 2015-10-18 02:59:56 |
| Message-ID: | 56230B2C.4050505@archidevsys.co.nz |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 18/10/15 00:13, Karsten Hilbert wrote:
> On Fri, Oct 16, 2015 at 04:59:12PM -0500, Jim Nasby wrote:
>
>> BTW, I found Karsten's idea of using 'pk' for the surrogate key, and
>> fk_table_name interesting. It helps avoid ambiguity from externally
>> generated ID values.
> That's the point :-)
>
> Here's a real live schema using (mostly) the above approach:
>
> http://www.gnumed.de/~ncq/gnumed/schema/gnumed_v20/
>
> in case anyone is interested in taking a look.
>
> Karsten
Hmm...
Apparently (according to your naming convention) several tables (such as
'clin.substance_intake') have 2 PRIMARY KEYs!!!
I guess you must have a large wall to display the schema on!
Looks like a lot of fun.
Can you tell us more about the database (ignoring nit-picking!)?
Cheers,
Gavin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Karsten Hilbert | 2015-10-18 09:32:35 | Re: ID column naming convention |
| Previous Message | Scott Mead | 2015-10-18 01:00:51 | Re: ID column naming convention |