From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | ddurst(at)larubber(dot)com |
Cc: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: LONG - Question on dealing w/ numerics |
Date: | 2003-01-29 09:01:39 |
Message-ID: | 21507.1043830899@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
"David Durst" <ddurst(at)larubber(dot)com> writes:
> But I still think your point about the function selecting more than
> one line is valid.
> The problem is, the journal_line_id is not created until the insert
> occurs and there is no other unique ident than the journal_line_id.
Well, my standard answer to that would be "your WHERE clause should
select on a primary key (which could be multiple columns)".
We're pretty constrained in changing the semantics of plpgsql, because
the raison d' etre of that language is to emulate Oracle's (TM) PL/SQL
(TM), warts and all.
(Now, if you can show us that PL/SQL behaves differently in that
situation, we'll definitely be willing to change plpgsql.)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | David Durst | 2003-01-29 09:17:51 | Re: LONG - Question on dealing w/ numerics |
Previous Message | Bruno Wolff III | 2003-01-29 08:31:05 | Re: converting microsoft sql server 2000 sql-code for postgresql |