Re: [PATCH] Datatype of OID should be VARBINARY, not INT - Mailing list pgsql-interfaces

From Tom Lane
Subject Re: [PATCH] Datatype of OID should be VARBINARY, not INT
Date
Msg-id 8051.961179817@sss.pgh.pa.us
Whole thread Raw
In response to Re: [PATCH] Datatype of OID should be VARBINARY, not INT  (Nissim <nissim@nksystems.com>)
List pgsql-interfaces
Nissim <nissim@nksystems.com> writes:
> Tom Lane wrote:
>> 
>> Nissim <nissim@nksystems.com> writes:
>>>> The datatype returned by the ResultSetMetaData for OID should be
>>>> VARBINARY, not INT.
>> 
>> Uh, why?  There's nothing VAR about it that I can see, and it is
>> the same size as INT ... at the moment anyway ...

> If you're using it to identify rows then it is used like an int, but if
> you're using it to point to a Large Object, the LO is variable size
> binary data, right?

The LO may be, but that doesn't make the OID so.  I think you are
confusing two things that should be kept separate.

> Will returning VARBINARY as the type of an OID column break anyone elses
> apps?

Undoubtedly.  Find another way.
        regards, tom lane


pgsql-interfaces by date:

Previous
From: Nissim
Date:
Subject: Re: [PATCH] Datatype of OID should be VARBINARY, not INT
Next
From: "Adam Rossi"
Date:
Subject: ODBC longvarchar error - why does this not work?