Re: Bug #513: union all changes char(3) column definition

Поиск
Список
Период
Сортировка
От Bruce Momjian
Тема Re: Bug #513: union all changes char(3) column definition
Дата
Msg-id 200111220413.fAM4DSH15042@candle.pha.pa.us
обсуждение исходный текст
Ответ на Re: Bug #513: union all changes char(3) column definition  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-bugs
> How many special cases like that do you want to put into the allegedly
> datatype-independent CREATE TABLE code?
> 
> If I thought this were the only case then I'd not object ... but it
> looks like a slippery slope from here.
> 
> And --- it's not like replacing "bpchar" with "text" actually buys us
> any useful new functionality.  AFAICS it's just a cosmetic thing.
> 
>             regards, tom lane
> 
> PS: On the other hand, we might consider attacking the problem from
> the reverse direction, ie *removing* code.  For example, if there
> weren't redundant || operators for char and varchar, then every ||
> operation would yield text, and the example we're looking at would
> work the way you want for free.  I've thought for awhile that we
> could use a pass through pg_proc and pg_operator to remove some
> entries we don't really need.

Can we convert bpchar to text in create table if no typmod is supplied?

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026
 


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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: Bug #513: union all changes char(3) column definition
Следующее
От: Ashley Cambrell
Дата:
Сообщение: Re: Bug #517: TO_CHAR(timestamp, 'Day') adds extra whitespace