From: Vlad Dimitriu <vlad.dimitriu@base.ro>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-sql@postgresql.org
Subject: Re: Exception handling from trigger
Date: Mon, 09 Aug 2004 20:38:36 +0300
Message-ID: <4117B69C.8080104@base.ro> (raw)
In-Reply-To: <16661.1092071643@sss.pgh.pa.us>
References: <4117AA90.9080704@base.ro>
<16661.1092071643@sss.pgh.pa.us>
Tom Lane wrote:
>You can't. From a logical perspective this is sensible, because the
>trigger is handed data already formed into a tuple. If the presented
>tuple contained a mycolumn value wider than 64 characters then it would
>not be a legal value of the rowtype (any more than if, say, the column
>value were an integer and not a varchar at all).
>
>What I'd suggest if you want this is to remove the datatype restriction
>and instead rely on your trigger to enforce the limitation.
>
>
>
I just realised that. I would design those columns as text
and enforce value length restrictions with triggers.
It's a false problem: I define the data type for a field and
want to check his value after the exception that I can't fit
larger data into my field.
Thank you, Rod, Tom ....
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: vlad.dimitriu@base.ro, tgl@sss.pgh.pa.us
Subject: Re: Exception handling from trigger
In-Reply-To: <4117B69C.8080104@base.ro>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox