Re: [HACKERS] char(8) vs char8

From: "Thomas G(dot) Lockhart" <lockhart(at)alumni(dot)caltech(dot)edu>
To: "D'Arcy J(dot)M(dot) Cain" <darcy(at)druid(dot)net>
Cc: hackers(at)postgresql(dot)org
Subject: Re: [HACKERS] char(8) vs char8
Date: 1998-05-14 15:27:18
Message-ID: 355B0D56.273FEEA8@alumni.caltech.edu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> This was an unexpected difference between these two types and I wonder
> if it was meant to be this way. Previously, a char8 field with the
> string 'abc' would return 'abc' as expected. Now, with char(8), I get
> back 'abc ' instead. You can see this with my PygreSQL module
> or the C interface (which my module uses, of course.) This causes a
> lot of my programs to break.
>
> I have made a quick change to my Python module to handle this. Should
> I clean it up or can I expect the behaviour to go back the way it was?

The behavior you want is varchar() rather than char().

- Tom

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message D'Arcy J.M. Cain 1998-05-14 17:10:44 Re: [HACKERS] char(8) vs char8
Previous Message Gran Thyni 1998-05-14 15:25:10 Re: AW: [HACKERS] mmap and MAP_ANON