From: | Jan Wieck <janwieck(at)yahoo(dot)com> |
---|---|
To: | Johann Zuschlag <zuschlag(at)online(dot)de> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>, Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
Subject: | Re: Why does this not work? |
Date: | 2002-04-11 18:53:01 |
Message-ID: | 200204111853.g3BIr1P05854@saturn.janwieck.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Johann Zuschlag wrote:
> On Thu, 11 Apr 2002 10:54:42 -0700 (PDT), Stephan Szabo wrote:
>
> >> -- Trigger: laenge_trig ON test
> >> CREATE TRIGGER "laenge_trig" BEFORE INSERT OR UPDATE ON "test" FOR
> >> EACH ROW EXECUTE PROCEDURE laenge();
> >>
> >> insert into test (test1) values ('0123456789012');
> >>
> >> value too long for type character varying(10)
> >
> >The value is being coerced into the type before your trigger
> >runs to be put into the values you're testing and it fails
> >at that point.
>
> Is there a solution for such a problem?
> Let's assume you can't be sure whether you get
> the appropriate length in an insert.
Create the table field as VARCHAR without a maximum size.
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck(at)Yahoo(dot)com #
From | Date | Subject | |
---|---|---|---|
Next Message | Johann Zuschlag | 2002-04-11 19:24:08 | Re: Why does this not work? (finally) |
Previous Message | Tom Lane | 2002-04-11 18:45:06 | Re: Why does this not work? |