RE: Enforcing uniqueness on [real estate/postal] addresses

From: Rich Shepard <rshepard(at)appl-ecosys(dot)com>
To: "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: RE: Enforcing uniqueness on [real estate/postal] addresses
Date: 2020-05-13 14:01:15
Message-ID: alpine.LNX.2.20.2005130659120.28549@salmo.appl-ecosys.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, 13 May 2020, Basques, Bob (CI-StPaul) wrote:

> Was wondering if you ever thought about binding the textual address to a
> USNG location. https://usngcenter.org/

Bobb, et al.:

Why not have a 'parent' table with entries such as 'Foo Farm' and a 'child'
table with rows for sub-parts of the parent; e.g., 'Barn', 'Field'?

Rich

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2020-05-13 14:15:42 Re: ESQL/C: a ROLLBACK rolls back a COMMITED transaction
Previous Message David Goodenough 2020-05-13 14:00:02 Re: Enforcing uniqueness on [real estate/postal] addresses