The following bug has been logged online:
Bug reference: 1839
Logged by: Matt
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.3
Operating system: linux
Description:insert into table (column) values (nullif('',''));
Details:
insert into table (column) values
Judith Altamirano <[EMAIL PROTECTED]> writes:
> Sorry, I just looked into the copyright, but the version that I'm currently
> used is POstgres 7.0.2, that is anyway ancient, :( , but the bug is also
> the same:
> IndexSupportInitialize: corrupted catalos
> do you think that there is a way to
On Sun, 21 Aug 2005, Matt wrote:
>
> The following bug has been logged online:
>
> Bug reference: 1839
> Logged by: Matt
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.0.3
> Operating system: linux
> Description:insert into table (column) values (nullif('',
On Sun, Aug 21, 2005 at 06:17:28PM +0100, Matt wrote:
>
> insert into table (column) values (nullif('',''));
> ERROR: column "column" is of type boolean but
> expression is of type text.
>
> inserting NULL works. nullif('','') should return NULL
> if both values are equal? It works in MSSQL.
NUL
"Matt" <[EMAIL PROTECTED]> writes:
> insert into table (column) values (nullif('',''));
> ERROR: column "column" is of type boolean but
> expression is of type text.
Seems reasonable to me. What type would you expect '' to be?
> It works in MSSQL.
If you think silent conversions from text to bo
FWIW, I edited the mappings under
src/backend/utils/mb/Unicode, added the character mappings and rebuilt
postgres to make the characters imported correctly.
Learning more about the problem, it seemed that there is no 100%
standard for mapping certain characters and everyone sort of does them
how t
