Re: Enforce primary key on every table during dev?

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Daevor The Devoted <dollien(at)gmail(dot)com>
Cc: Ron Johnson <ron(dot)l(dot)johnson(at)cox(dot)net>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Enforce primary key on every table during dev?
Date: 2018-03-01 20:12:21
Message-ID: CAKFQuwbHb27SYAx9ozYjE4Xa92-u9XhBvFOQAJ1GC+GX1cUjNQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, Mar 1, 2018 at 1:06 PM, Daevor The Devoted <dollien(at)gmail(dot)com>
wrote:

>
>> This seems like hierarchical data
>

​Hence the "this is contrived" disclaimer - but if one allows for
employee-department to be many-to-many, and thus requiring a joining table,
this still applies even if the specific choice to nouns doesn't make sense.

David J.
​

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Ron Johnson 2018-03-01 20:21:18 Re: Enforce primary key on every table during dev?
Previous Message Daevor The Devoted 2018-03-01 20:09:30 Re: Enforce primary key on every table during dev?