From: | Chris <chrisb(at)nimrod(dot)itg(dot)telstra(dot)com(dot)au> |
---|---|
To: | "pgsql-hackers(at)postgreSQL(dot)org" <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Tom Lane |
Date: | 2000-09-06 05:42:02 |
Message-ID: | 39B5D92A.5323D4F4@nimrod.itg.telecom.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom, the following was said in the apache turbine project mailing list a
while back regarding telling the difference between an ordinary oid
column and an oid column that points to a large object. Can you confirm
if this is true regarding the reference to change in v 7.1 ?
--
"That's why they didn't want my patch which changed the SQL Type
returned by the metadata from Integer to Varbinary, because it'll break
anybody who uses it as an int (which is what it really is). But the
problem is that there is no datatype called, "Image" or "varbinary," the
only way you can use a large object field is by setting the column
datatype to OID. It's ambiguous...I don't use that datatype for
anything but large objects, so the patch works for me, but I understand
why they don't want it in the main dist. of the driver.
Tom Lane from the pgsql team told me that in v 7.1 there will be a way
to identify the difference between a binary column and an oid column."
--
From | Date | Subject | |
---|---|---|---|
Next Message | Mike Mascari | 2000-09-06 05:47:05 | Re: Fragged State in 7.0.2 |
Previous Message | Tom Lane | 2000-09-06 05:27:15 | Re: UNION/INTERSECT in subselects |