Re: BUG #1956: Plpgsql top-level DECLARE does not share scope

Поиск
Список
Период
Сортировка
От Klint Gore
Тема Re: BUG #1956: Plpgsql top-level DECLARE does not share scope
Дата
Msg-id 4352F3DF22A.0024KG@129.180.47.120
обсуждение исходный текст
Ответ на Re: BUG #1956: Plpgsql top-level DECLARE does not share scope  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-bugs
On Thu, 13 Oct 2005 16:24:23 -0400, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> BTW, another issue here is that if we did merge the first DECLARE with
> the scope of auto-declared variables, it would be a non backwards
> compatible change.  Right now you can do, say,
>
>     declare found int;
>
> and it'll override the standard FOUND variable.  If we change this then
> you'd get an error.  (Of course, it could be argued that that would be
> a Good Thing.  But it would inhibit us from adding new auto-declared
> variables that are less central to the language than FOUND, because of
> the risk of breaking existing code.)

Could something be done using alias?

eg
declare x int;
...
   declare x alias for outer x


klint.

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

Предыдущее
От: Martin Pitt
Дата:
Сообщение: Re: BUG #1963: SSL certificate permission check is too strict
Следующее
От: Tom Lane
Дата:
Сообщение: Re: [GENERAL] Postgres logs to syslog LOCAL0