Received: from sss2.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2]) by hub.org (8.10.1/8.10.1) with ESMTP id e5GINlM68124 for ; Fri, 16 Jun 2000 14:23:47 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss2.sss.pgh.pa.us (8.9.3/8.9.3) with ESMTP id OAA08054; Fri, 16 Jun 2000 14:23:38 -0400 (EDT) To: Nissim cc: pgsql-interfaces@postgresql.org Subject: Re: [PATCH] Datatype of OID should be VARBINARY, not INT In-reply-to: <394A6A56.ADFC63A2@nksystems.com> References: <394A3D07.C1542D05@nksystems.com> <7249.961167897@sss.pgh.pa.us> <394A6A56.ADFC63A2@nksystems.com> Comments: In-reply-to Nissim message dated "Fri, 16 Jun 2000 13:56:38 -0400" Date: Fri, 16 Jun 2000 14:23:37 -0400 Message-ID: <8051.961179817@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200006/74 Nissim writes: > Tom Lane wrote: >> >> Nissim 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