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 1pgS4C-0002hK-Tn for pgsql-novice@arkaria.postgresql.org; Sun, 26 Mar 2023 15:13:56 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pgS4B-0002IU-04 for pgsql-novice@arkaria.postgresql.org; Sun, 26 Mar 2023 15:13:55 +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 1pgS4A-0002HM-NX for pgsql-novice@lists.postgresql.org; Sun, 26 Mar 2023 15:13:54 +0000 Received: from mail-ed1-x52f.google.com ([2a00:1450:4864:20::52f]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1pgS48-0007Uj-CS for pgsql-novice@lists.postgresql.org; Sun, 26 Mar 2023 15:13:54 +0000 Received: by mail-ed1-x52f.google.com with SMTP id ek18so25987153edb.6 for ; Sun, 26 Mar 2023 08:13:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1679843631; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=/eC+IhsKSdzGQ+UquLkc1FzekIRXzD9K2K1EIAQhxs0=; b=giC4rdMvQgqmaIpyJk53cs5IyZJWx8aLmcVMnww5KZOGPh7+ot/yRwhyu4iu5MLlma 42DX1S9Xdf97CZ9H7G3q07GL//3VliHm0qSxV9qxlDNqlV32Y1/3ntVpwD2ffp9RQH90 VfeDwP8oCWudWQ4vGWNzmz0TmL3qcQVjoD+yGt3sHiZrYPbr78ul9DHnVWc3+fOZ6AYI sSORrxKtjCo54CWbs6Kix/OmkJrv4YPEBi8JC2jbwnJ1gEmatimLEL3hxm8zC5hiUOLl HkquNaABzHKu8J876S+cJLQnyHVTz0y8Bvk/X9lnTlZjMoCezF/266mcZCgJyiPK0jpG 7L7g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1679843631; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=/eC+IhsKSdzGQ+UquLkc1FzekIRXzD9K2K1EIAQhxs0=; b=4yD7hmRY7Z0kDc4dHGMq2vomJ6gLOGXBYptEZkkzFh54bTTN7PVayJAHPqi0gnjubX cKrRhUb8M8Mn/L9NkFnh574mMC4R0ceQzPeKoyo/69rqhkQIQvRjvJHnGXE6mbSAuLWH lk6aShII5EoVtjUCUX8wPslDI4RoclFGYIViNs5JugcKPcEoAkSHUfQ+FHghTA9d3gB5 nVP1EDZ3q34nHxmFbpUWNWqdVmWMV37Y/RU0Ve/OsYV18eL8ORgylGhq83iGrglXSLSS TFmLpxWUHUUrE3xVXxhx6dOrdnoM25semvZr3eXPlnIwAJWNREjjHSnsMZyjl5zkyUW2 wS7g== X-Gm-Message-State: AAQBX9ezRG3hwJlwInoxWa98A3F+91xhgVPpnR1fUZCUQcy60gwHn54V vc30Ro2fWs6AnuOQ9g6KfuIrOl76ml5GptW4WRA= X-Google-Smtp-Source: AKy350bG1jHNN5tIIeOzH8FmV7AFxCdm8wGAOLbCxI2D0JecSjwxyw7D3t+tkEsCFvuWQCJq0uVSwC7pYn+xnVqg6TI= X-Received: by 2002:a50:a6d1:0:b0:4fa:794a:c0cc with SMTP id f17-20020a50a6d1000000b004fa794ac0ccmr4659821edc.2.1679843631005; Sun, 26 Mar 2023 08:13:51 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a98:ccd0:0:b0:1a0:6697:addf with HTTP; Sun, 26 Mar 2023 08:13:50 -0700 (PDT) In-Reply-To: References: From: "David G. Johnston" Date: Sun, 26 Mar 2023 08:13:50 -0700 Message-ID: Subject: Re: How to get column, table or parameter name reporting when violating DOMAIN type constraint To: Valerio Battaglia Cc: "pgsql-novice@lists.postgresql.org" Content-Type: multipart/alternative; boundary="000000000000e7846905f7cf1265" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000e7846905f7cf1265 Content-Type: text/plain; charset="UTF-8" On Sunday, March 26, 2023, Valerio Battaglia wrote: > > Is there a way to obtain more detailed information about the column, table > or parameter that is causing the constraint violation in this scenario? I > would greatly appreciate any guidance or advice you could provide on this > matter > What you see is what you get. David J. --000000000000e7846905f7cf1265 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sunday, March 26, 2023, Valerio Battaglia <vabatta@gmail.com> wrote:
<= div dir=3D"ltr">

Is there a way to obtain more detailed in= formation about the column, table or parameter that is causing the constrai= nt violation in this scenario? I would greatly appreciate any guidance or a= dvice you could provide on this matter


What you see is what you get.

<= div>David J.
=C2=A0
--000000000000e7846905f7cf1265--