Re: [HACKERS] Assignment of valid collation for SET operations onqueries with UNKNOWN types.

Поиск
Список
Период
Сортировка
От Michael Paquier
Тема Re: [HACKERS] Assignment of valid collation for SET operations onqueries with UNKNOWN types.
Дата
Msg-id CAB7nPqTqzetKOmJ_ErtHMtbRUkjbRU4hswh-oVOgtqeifOuOgg@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [HACKERS] Assignment of valid collation for SET operations onqueries with UNKNOWN types.  (Rahila Syed <rahilasyed90@gmail.com>)
Список pgsql-hackers
On Wed, Dec 14, 2016 at 7:02 PM, Rahila Syed <rahilasyed90@gmail.com> wrote:
>>There is a similar code pattern for materialized views, see
>>create_ctas_nodata() where the attribute list is built
> create_ctas_nodata() is for creation of materialized views WITH NO DATA.
> For other materialized views and CREATE TABLE AS, column definitions are
> built in
> intorel_startup() function which has different code from that of CREATE VIEW
> which
> the patch deals with.
>
> Limiting the scope of the patch to include changing the type of literal
> constants
> to text only for plain views. Also, error out when column with UNKNOWN type
> is
> being created for other relations like tables and materialized views.

Matviews is the same way of thinking as views in terms of definition.
It is inconsistent to try to address a problem only partially if the
same behavior shows up in different code paths.
-- 
Michael



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

Предыдущее
От: Rahila Syed
Дата:
Сообщение: Re: [HACKERS] Assignment of valid collation for SET operations onqueries with UNKNOWN types.
Следующее
От: Michael Paquier
Дата:
Сообщение: Re: pg_authid.rolpassword format (was Re: [HACKERS] Passwordidentifiers, protocol aging and SCRAM protocol)