Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1qIgb0-0002Dl-3I for pgsql-general@arkaria.postgresql.org; Mon, 10 Jul 2023 02:25:50 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1qIgay-0001kz-Vw for pgsql-general@arkaria.postgresql.org; Mon, 10 Jul 2023 02:25:48 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1qIgay-0001kq-9z for pgsql-general@lists.postgresql.org; Mon, 10 Jul 2023 02:25:48 +0000 Received: from rs6162.luxsci.com ([162.142.76.255]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qIgau-003CJf-DT for pgsql-general@lists.postgresql.org; Mon, 10 Jul 2023 02:25:47 +0000 Received: from pfortin.com (h231.250.89.75.dynamic.ip.windstream.net [75.89.250.231]) (authenticated bits=0) by rs6162.luxsci.com (8.15.2/8.14.9) with ESMTPSA id 36A2PdhF567012 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NOT) for ; Mon, 10 Jul 2023 02:25:40 GMT Date: Sun, 9 Jul 2023 22:25:39 -0400 From: pf@pfortin.com To: pgsql-general@lists.postgresql.org Subject: Re: INSERT UNIQUE row? Message-ID: <20230709222539.116ee4b8@pfortin.com> In-Reply-To: <0b2061ad-1a27-d2df-44f6-3af87edf9b6e@aklaver.com> References: <20230709185807.1bc9afd9.pfortin@pfortin.com> <0b2061ad-1a27-d2df-44f6-3af87edf9b6e@aklaver.com> X-Mailer: Claws Mail 4.1.1git47 (GTK 3.24.38; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Lux-Comment: Message 36A2PdhF567012 sent by user #22429 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pfortin.com; h=date:from:to:subject:message-id:in-reply-to:references:mime-version:content-type:content-transfer-encoding; s=dkim; bh=PKOGQLSM5X1GZRCsfRMWHqIZ77hYtLHi1otLuH2mP8g=; b=zybHM1ryaiob26G6xrLCaLEZtccmrauhTc6qXFlMV54rWGm4IdfAjbr39fZgX08GUGgH0GZfiRZICum14K//hnZqtLQe6jezyRlk9YleuI6fAdutMLaQ2rSrLwoI9va8ApPfj86pabV/2uJHdEnW1v7hZFB0qGtdmSLeu5IAvNQ= List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Sun, 9 Jul 2023 17:04:03 -0700 Adrian Klaver wrote: >On 7/9/23 15:58, pf@pfortin.com wrote: >> Hi, >> >> Trying to figure out how to insert new property addresses into an >> existing table. >> >> Can a UNIQUE constraint be applied to an entire row? Adding UNIQUE to >> each column won't work in such a case since there are multiple properties >> * on the same street >> * in the same town >> * with the same number on different streets >> * etc... > >Does the locality you are in have something like the Property ID# and/or >Parcel # / Geo ID shown here: > >https://property.whatcomcounty.us/propertyaccess/PropertySearch.aspx?cid=0 Thanks! Just getting started on this issue and this made me realize my current data source may not be the best... Much appreciated! >> >> Each row is only unique as an entity; but the columns are not... >> >> Is this covered in the docs? >> >> Thanks, >> Pierre >> >> >> >