On 2020-05-12 21:55:56 +0100, Peter Devoy wrote:
> >Is is possible to have two entries which have the same
> >address_identifier_general, street and postcode, but different
> >descriptions?
>
> Unfortunately, yes. The data comes from gov't systems to
> regulate the development/alteration of arbit
: Peter J. Holzer
> Cc: pgsql-general@lists.postgresql.org
> Subject: Re: Enforcing uniqueness on [real estate/postal] addresses
>
> Think Before You Click: This email originated outside our organization.
>
>
>
> >Is is possible to have two entries which have the same
AM
To: pgsql-general@lists.postgresql.org
Subject: RE: Enforcing uniqueness on [real estate/postal] addresses
Think Before You Click: This email originated outside our organization.
On Wed, 13 May 2020, Basques, Bob (CI-StPaul) wrote:
> Was wondering if you ever thought about binding the textual
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 p
: pgsql-general@lists.postgresql.org
Subject: Re: Enforcing uniqueness on [real estate/postal] addresses
Think Before You Click: This email originated outside our organization.
>Is is possible to have two entries which have the same
>address_identifier_general, street and postcode, but different
>desc
On 5/12/20 1:55 PM, Peter Devoy wrote:
Is is possible to have two entries which have the same
address_identifier_general, street and postcode, but different
descriptions?
Unfortunately, yes. The data comes from gov't systems to
regulate the development/alteration of arbitrary pieces of propert
On Tue, 12 May 2020, Peter Devoy wrote:
Is is possible to have two entries which have the same
address_identifier_general, street and postcode, but different
descriptions?
Unfortunately, yes. The data comes from gov't systems to regulate the
development/alteration of arbitrary pieces of proper
On Tue, May 12, 2020 at 09:55:56PM +0100, Peter Devoy wrote:
> >Is is possible to have two entries which have the same
> >address_identifier_general, street and postcode, but different
> >descriptions?
>
> Unfortunately, yes. The data comes from gov't systems to
> regulate the development/alterat
>Is is possible to have two entries which have the same
>address_identifier_general, street and postcode, but different
>descriptions?
Unfortunately, yes. The data comes from gov't systems to
regulate the development/alteration of arbitrary pieces of property and
those pieces do not always have a
On 2020-05-12 10:49:22 +1000, Tim Cross wrote:
> Peter Devoy writes:
> > I need to store addresses for properties (as in real estate) so in my
> > naivety I created a unique constraint like this:
> >
> > ALTER TABLE properties
> > ADD CONSTRAINT is_unique_address
> > UNIQUE (
> > d
Peter Devoy writes:
> Hi list
>
> I need to store addresses for properties (as in real estate) so in my
> naivety I created a unique constraint like this:
>
> ALTER TABLE properties
> ADD CONSTRAINT is_unique_address
> UNIQUE (
> description, --e.g. Land north of Foo Cottage
>
Hello everyone
Thank you all for your suggestions. I had neither heard of partial
unique indexes nor
considered using COALESCE so I will explore both of these as options
and update the
thread with how it goes.
>Then, if you can define a problem where you feel having a unique table
>constraint o
On 5/11/20 9:55 AM, Peter Devoy wrote:
Of course, if any of the fields are NULL (which they often are) I end
up with duplicates.
One solution may be to add NOT NULL constraints and use empty strings
instead of NULL values but, until asking around today, I thought this was
generally considered ba
On Mon, May 11, 2020 at 9:56 AM Peter Devoy wrote:
> I need to store addresses for properties (as in real estate) so in my
> naivety I created a unique constraint like this:
>
> ALTER TABLE properties
> ADD CONSTRAINT is_unique_address
> UNIQUE (
> description, --e.g. Land north o
On 5/11/20 9:55 AM, Peter Devoy wrote:
Hi list
I need to store addresses for properties (as in real estate) so in my
naivety I created a unique constraint like this:
ALTER TABLE properties
ADD CONSTRAINT is_unique_address
UNIQUE (
description, --e.g. Land north of Foo Cottage
> On May 11, 2020, at 12:55 PM, Peter Devoy wrote:
>
> Hi list
>
> I need to store addresses for properties (as in real estate) so in my
> naivety I created a unique constraint like this:
>
> ALTER TABLE properties
>ADD CONSTRAINT is_unique_address
>UNIQUE (
>description, --e
16 matches
Mail list logo
