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

Поиск
Список
Период
Сортировка
От Pavel Stehule
Тема Re: Relax requirement for INTO with SELECT in pl/pgsql
Дата
Msg-id CAFj8pRBcQ6FbS2t1KypNk_7Tpkg8y143C=aAj531VvUzSFrVNg@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Relax requirement for INTO with SELECT in pl/pgsql  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
Список pgsql-hackers


2016-03-21 23:26 GMT+01:00 Jim Nasby <Jim.Nasby@bluetreble.com>:
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.

We are support

var := (query expression)

and this syntax is required and supported by ANSI/SQL - there are no any reason to support other proprietary extension.

Regards

Pavel

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 по дате отправления:

Предыдущее
От: Pavel Stehule
Дата:
Сообщение: Re: Relax requirement for INTO with SELECT in pl/pgsql
Следующее
От: Pavel Stehule
Дата:
Сообщение: Re: Relax requirement for INTO with SELECT in pl/pgsql