Re: PL/pgSQL 1.2 - Mailing list pgsql-hackers

From Shaun Thomas
Subject Re: PL/pgSQL 1.2
Date
Msg-id 5408728D.30902@optionshouse.com
Whole thread Raw
In response to Re: PL/pgSQL 1.2  (Hannu Krosing <hannu@2ndQuadrant.com>)
Responses Re: PL/pgSQL 1.2  (Marko Tiikkaja <marko@joh.to>)
List pgsql-hackers
On 09/03/2014 04:19 PM, Hannu Krosing wrote:

> 1. Conditions for number of rows returned by SELECT or touched by
> UPDATE or DELETE

Now that I think upon this... don't we already have it?

SELECT ... LIMIT 1

That already solves the purported problem of multiple results in SELECT 
INTO as well. Could we possibly extend that to UPDATE and DELETE syntax too?

-- 
Shaun Thomas
OptionsHouse, LLC | 141 W. Jackson Blvd. | Suite 800 | Chicago IL, 60604
312-676-8870
sthomas@optionshouse.com

______________________________________________

See http://www.peak6.com/email_disclaimer/ for terms and conditions related to this email



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Escaping from blocked send() reprised.
Next
From: Marko Tiikkaja
Date:
Subject: Re: PL/pgSQL 1.2