Re: Relax requirement for INTO with SELECT in pl/pgsql

Поиск
Список
Период
Сортировка
От Jim Nasby
Тема Re: Relax requirement for INTO with SELECT in pl/pgsql
Дата
Msg-id 56F07529.8010806@BlueTreble.com
обсуждение исходный текст
Ответ на Re: Relax requirement for INTO with SELECT in pl/pgsql  (Merlin Moncure <mmoncure@gmail.com>)
Ответы Re: Relax requirement for INTO with SELECT in pl/pgsql  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Relax requirement for INTO with SELECT in pl/pgsql  (Pavel Stehule <pavel.stehule@gmail.com>)
Список pgsql-hackers
On 3/21/16 5:03 PM, Merlin Moncure wrote:
> in Oracle, you'd simply do:
> LogIt('I did something');

It would be *great* if we could support that in plpgsql.

> I'm not sure what Oracle does for SELECT statements without INTO/BULK
> UPDATE.  I'm not really inclined to care -- I'm really curious to see
> an argument where usage of PERFORM actually helps in some meaningful
> way.  Notably, SELECT without INTO is accepted syntax, but fails only
> after running the query.  I think that's pretty much stupid but it's
> fair to say I'm not inventing syntax, only disabling the error.

I don't think it buys much at all.

While we're on the subject, it'd be great if variable := SELECT ... 
worked too.

> I'm not sure what other databases do is relevant.   They use other
> procedure languages than pl//sql (the biggest players are pl/psm and
> t-sql) which have a different set of rules in terms of passing
> variables in and out of queries.

+1
-- 
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Alvaro Herrera
Дата:
Сообщение: Re: WIP: Access method extendability
Следующее
От: Stephen Frost
Дата:
Сообщение: Re: Minor bug affecting ON CONFLICT lock wait log messages