Re: 'text' instead of 'unknown' in Postgres 10

From: Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>
To: Daniele Varrazzo <daniele(dot)varrazzo(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: 'text' instead of 'unknown' in Postgres 10
Date: 2017-02-13 03:09:35
Message-ID: 95c24803-0d82-f6c1-72a7-3472d8f07dea@BlueTreble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2/7/17 9:16 AM, Daniele Varrazzo wrote:
> Thank you for the clarification: I will assume the behaviour cannot be
> maintained on PG 10 and think whether the treatment of '{}' is too
> magical and drop it instead.

BTW, I would hope that passing '{}' into a defined array field still
works, since an empty array isn't treated the same as NULL, which means
you need some way to create an empty array.
--
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
855-TREBLE2 (855-873-2532)

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jim Nasby 2017-02-13 03:21:16 Re: Time to up bgwriter_lru_maxpages?
Previous Message Jim Nasby 2017-02-13 02:58:26 Re: drop support for Python 2.3