Re: Surprising (?) Sequence Behavior

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: Surprising (?) Sequence Behavior
Дата
Msg-id 7237.1201554804@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Surprising (?) Sequence Behavior  ("Richard M. Kues" <software@riva.at>)
Ответы Re: Surprising (?) Sequence Behavior  ("Richard M. Kues" <software@riva.at>)
Список pgsql-general
"Richard M. Kues" <software@riva.at> writes:
> CREATE TEMPORARY SEQUENCE s;

> SELECT
>     nextval('s'), t.name
> FROM
> (
>     SELECT
>        tablename AS name
>     FROM
>        pg_tables
>     ORDER BY
>        tablename
> ) AS t
> WHERE
>     t.name = 'pg_am'
> ;

> The result is:
>     1 pg_am

> instead of:
>     2 pg_am

> At least for me this is surprising!

Why do you find it surprising?  Per spec, the SELECT output list is not
evaluated at rows that fail the WHERE clause.  This must be so; consider
examples like
    SELECT 1/x FROM t WHERE x <> 0;

I think what you need is three levels of nested SELECT, with the
nextval() done in the middle level, and probably an "OFFSET 0" in the
middle one to keep Postgres from collapsing the top and middle together.

            regards, tom lane

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

Предыдущее
От: Decibel!
Дата:
Сообщение: Re: [pgsql-advocacy] PostgreSQL professionals group at LinkedIn.com
Следующее
От: Tom Lane
Дата:
Сообщение: Re: handling of COUNT(record) vs IS NULL