| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Vlad Dimitriu <vlad(dot)dimitriu(at)base(dot)ro> |
| Cc: | pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: Exception handling from trigger |
| Date: | 2004-08-09 17:14:03 |
| Message-ID: | 16661.1092071643@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
Vlad Dimitriu <vlad(dot)dimitriu(at)base(dot)ro> writes:
> I would like to handle the exceptions that a database returns. For example,
> if a "mycolumn" column is defined as varchar(64), I'd like to catch
> if the new.mycolumn is larger than 64 with my own trigger
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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2004-08-09 17:33:47 | Re: surrogate keys and replication. |
| Previous Message | Rod Taylor | 2004-08-09 16:52:54 | Re: Exception handling from trigger |