On Fri, 2005-08-12 at 21:53 -0400, Bruce Momjian wrote:
This has been saved for the 8.2 release:
Just to clarify: the SELECT INTO EXACT patch was abandoned in favor of
the #option select_into_1_row patch. I submitted both patches as part
of the same -patches thread, but the latter solution, the
On Tue, 2005-08-09 at 15:01 +, Matt Miller wrote:
Attached is a patch that implements the #option select_into_1_row
directive as suggested.
Is this patch good-to-go? Can it be queued?
---(end of broadcast)---
TIP 4: Have you searched our
PIf you're really desparate, you can increase the pagesize a bit (to
Should be desperate, not desparate.
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
On Mon, 2005-08-08 at 17:18 -0400, Tom Lane wrote:
If you think that this should be a global option instead of a
per-statement one, something like the (undocumented) #option hack might
be a good way to specify it; that would give it per-function scope,
which seems reasonable.
create
On Fri, 2005-07-29 at 17:52 -0400, Tom Lane wrote:
Matt Miller [EMAIL PROTECTED] writes:
This patch implements an optional EXACT keyword after the INTO keyword
of the PL/pgSQL SELECT INTO command. ... when SELECTing INTO ...
leave the targets untouched if the query does not
return
On Mon, 2005-08-08 at 17:18 -0400, Tom Lane wrote:
Matt Miller [EMAIL PROTECTED] writes:
On Fri, 2005-07-29 at 17:52 -0400, Tom Lane wrote:
I dislike the choice of EXACT, too, as it (a) adds a new reserved word
and (b) doesn't seem to convey quite what is happening anyway. Not sure
about
This was motivated by the SELECT INTO EXACT discussion at
http://archives.postgresql.org/pgsql-patches/2005-07/msg00559.php.
The idea is to allow a PL/pgSQL exception to not automatically rollback
the work done by the current block. The benefit is that exception
handling can be used as a program
On Wed, 2005-08-03 at 16:25 -0400, Tom Lane wrote:
The idea is to allow a PL/pgSQL exception to not automatically
rollback the work done by the current block.
This fundamentally breaks the entire backend.
Yeah, but besides that, can you quick commit this to HEAD so I don't
have to keep
This patch implements an optional EXACT keyword after the INTO keyword
of the PL/pgSQL SELECT INTO command. The motivation is to come closer
to Oracle's SELECT INTO behavior: when SELECTing INTO scalar targets,
raise an exception and leave the targets untouched if the query does not
return
On Fri, 2005-07-29 at 17:52 -0400, Tom Lane wrote:
Matt Miller [EMAIL PROTECTED] writes:
The motivation is to come closer to Oracle's SELECT INTO
behavior: when SELECTing INTO scalar targets,
raise an exception and leave the targets untouched if the query does
not return exactly one row
The motivation is to come closer
to Oracle's SELECT INTO behavior: when SELECTing INTO scalar targets,
raise an exception and leave the targets untouched if the query does not
return exactly one row.
why that is not the default behavior of the SELECT INTO?
...
i mean, when you do that
11 matches
Mail list logo
