Skip site navigation (1) Skip section navigation (2)

Re: [PATCH] Datatype of OID should be VARBINARY, not INT

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Nissim <nissim(at)nksystems(dot)com>
Cc: pgsql-interfaces(at)postgresql(dot)org
Subject: Re: [PATCH] Datatype of OID should be VARBINARY, not INT
Date: 2000-06-16 18:23:37
Message-ID: 8051.961179817@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-interfaces
Nissim <nissim(at)nksystems(dot)com> writes:
> Tom Lane wrote:
>> 
>> Nissim <nissim(at)nksystems(dot)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

In response to

pgsql-interfaces by date

Next:From: Adam RossiDate: 2000-06-16 18:30:13
Subject: ODBC longvarchar error - why does this not work?
Previous:From: NissimDate: 2000-06-16 17:56:38
Subject: Re: [PATCH] Datatype of OID should be VARBINARY, not INT

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group