| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jaime Casanova <systemguards(at)yahoo(dot)com> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: a bug in plpgsql |
| Date: | 2004-11-04 20:28:25 |
| Message-ID: | 29373.1099600105@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Jaime Casanova <systemguards(at)yahoo(dot)com> writes:
> --- Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> escribi:
>> It most certainly did not work in 7.4.2, or any
>> other PG release.
>> plpgsql doesn't have a CASE statement.
> This is a production server... and the same script...
> (It was an error in v7.4.2 to permit this?)
Are you sure the function has ever been executed? 7.4 gives me
regression=# select recaudaciones.rec_f_aperturarcaja(1::int2,2::int2);
ERROR: syntax error at or near "ELSE"
CONTEXT: compile of PL/pgSQL function "rec_f_aperturarcaja" near line 51
8.0 is just reporting the error when the function is defined instead
of at first call.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jaime Casanova | 2004-11-04 20:36:50 | Re: a bug in plpgsql |
| Previous Message | Jaime Casanova | 2004-11-04 20:05:22 | Re: a bug in plpgsql |