From: | RABIN NATHAN <r_nathan(at)shaw(dot)ca> |
---|---|
To: | john snow <ofbizfanster(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-novice <pgsql-novice(at)postgresql(dot)org> |
Subject: | Re: why do i get 2 as answer for select length('aa '::char(6)); |
Date: | 2018-01-17 08:10:21 |
Message-ID: | 8FA2EC8C-636F-490D-A2AD-63D120E49DFB@shaw.ca |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
Does anybody know how I get of this list?
Rabindra Nathan from mobile device.
> On Jan 16, 2018, at 7:38 PM, john snow <ofbizfanster(at)gmail(dot)com> wrote:
>
> thanks! you are right. we're porting a 20 year old xbase app and it's painful
>
>> On Wed, Jan 17, 2018 at 11:32 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> john snow <ofbizfanster(at)gmail(dot)com> writes:
>> > when you say char-type values, do you include varchar?
>>
>> No. varchar and text consider trailing spaces to be significant.
>>
>> To my mind, there are very few situations where char(n) is actually
>> a reasonable choice of datatype. Maybe for US state abbreviations
>> or the like. If you're even asking this question, it suggests that
>> you ought to be using varchar/text.
>>
>> char(n) basically exists to support fixed-field-width data designs that
>> should have died along with the punched cards that inspired them.
>>
>> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | jlymarius@yahoo.com | 2018-01-17 21:05:11 | Restarting PostgreSQL 10.1 |
Previous Message | john snow | 2018-01-17 03:37:43 | Re: why do i get 2 as answer for select length('aa '::char(6)); |