From: Tom Lane <tgl@sss.pgh.pa.us>
To: Nissim <nissim@nksystems.com>
Cc: pgsql-interfaces@postgresql.org
Subject: Re: [PATCH] Datatype of OID should be VARBINARY, not INT
Date: Fri, 16 Jun 2000 14:23:37 -0400
Message-ID: <8051.961179817@sss.pgh.pa.us> (raw)
In-Reply-To: <394A6A56.ADFC63A2@nksystems.com>
References: <394A3D07.C1542D05@nksystems.com>
<7249.961167897@sss.pgh.pa.us>
<394A6A56.ADFC63A2@nksystems.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: tgl@sss.pgh.pa.us, nissim@nksystems.com
Subject: Re: [PATCH] Datatype of OID should be VARBINARY, not INT
In-Reply-To: <8051.961179817@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox