Re: bad typenames sent to postgresql server - Mailing list pgsql-odbc

From Dave Page
Subject Re: bad typenames sent to postgresql server
Date
Msg-id E7F85A1B5FF8D44C8A1AF6885BC9A0E43068DB@ratbert.vale-housing.co.uk
Whole thread Raw
In response to bad typenames sent to postgresql server  ("Scot Loach" <sloach@sandvine.com>)
List pgsql-odbc

> -----Original Message-----
> From: pgsql-odbc-owner@postgresql.org
> [mailto:pgsql-odbc-owner@postgresql.org] On Behalf Of Scot Loach
> Sent: 04 October 2004 22:11
> To: pgsql-odbc@postgresql.org
> Subject: [ODBC] bad typenames sent to postgresql server
>
> I've recently updated my CVS, and I'm now getting parsing
> errors from the backend when I use a PREPARE statement with
> varchar in the types clause.
> This seems to be because of the following changes made to
> pgtypes.c in version 1.63.
>
> I looked at the postgresql parser, and sure enough, the
> varchar(), char() etc are not accepted.
> Does anyone know what the intention of this change was?  (the
> comment says "Map (var)char type to SQL type more properly")
> Is this in fact a bug or am I missing something?

Bug I /think/. The brackets were added to numeric, varchar and char, all
of which might have them when defining tables etc, however, when used as
casts or in type clauses I'm not surprised there are problems.

I'm not sure why they were added though (although I don't doubt Hiroshi
had a good reason). Can anyone remember? If not, istm, that the best
solution is to remove them again from there, and add them again in less
generic places if the original problem is found again.

Regards, Dave.

pgsql-odbc by date:

Previous
From: "Dave Page"
Date:
Subject: Schema support
Next
From: anthony.caduto@micorp.com
Date:
Subject: Re: Schema support