From: | "Josh Berkus" <josh(at)agliodbs(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: Re: Inserts in triggers Follow Up |
Date: | 2001-07-25 15:53:45 |
Message-ID: | web-91242@davinci.ethosmedia.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-sql |
Tom,
> No, this isn't right. If you check the source code you will discover
> that plpgsql is extremely lax about the positioning of the INTO
> clause,
> and will in fact accept it almost anywhere. Datatype has nothing to
> do with this. (It probably should be stricter, but at this point I
> doubt we could change it without drawing howls of anguish from those
> who did it the other way.)
Thanks for setting me straight, Tom. I guess I combines some bugs in
7.0.2 with the original sketchy instructions and assumed that there were
stricter syntactical rules than there are.
This is good because it now means I can use the logical syntax of
SELECT data INTO var ...
which to me is easier to read, for everything.
-Josh
______AGLIO DATABASE SOLUTIONS___________________________
Josh Berkus
Complete information technology josh(at)agliodbs(dot)com
and data management solutions (415) 565-7293
for law firms, small businesses fax 621-2533
and non-profit organizations. San Francisco
Attachment | Content-Type | Size |
---|---|---|
unknown_filename | text/plain | 2 bytes |
unknown_filename | text/plain | 2 bytes |
unknown_filename | text/plain | 2 bytes |
From | Date | Subject | |
---|---|---|---|
Next Message | Lee Harr | 2001-07-25 15:57:46 | Re: pqReadData() -- backend closed the channel unexpectedly. |
Previous Message | Tom Lane | 2001-07-25 15:43:06 | Re: Re: Inserts in triggers Follow Up |
From | Date | Subject | |
---|---|---|---|
Next Message | Stephan Szabo | 2001-07-25 16:26:08 | Re: Meta integrity |
Previous Message | Tom Lane | 2001-07-25 15:43:06 | Re: Re: Inserts in triggers Follow Up |