| From: | Caio Begotti <caio(at)ueberalles(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-odbc(at)postgresql(dot)org |
| Subject: | Re: possible odbc driver bug with postgresql-7.4 |
| Date: | 2006-12-12 17:30:20 |
| Message-ID: | 1C34D1CC-0DAA-4ED3-9122-CC97DB3DEB2B@ueberalles.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-odbc |
On 12/12/2006, at 15:11, Tom Lane wrote:
> If you expect a read of the column to deliver a lot of bytes then you
> should be using bytea not large objects, I would think.
Talking to blitzrage, another reporter of this issue, minutes ago:
[15:26:24] blitzrage: its not the field type that is the issue -- its
how the current implementation pulls the data from the DB afaict
[15:26:47] blitzrage: the data is in the DB, but right now, the
implementation just pulls the OID out of the DB, not the blob
[15:27:09] blitzrage: I tried all binary types -- that's not the issue
He refused to join this list, so I believe I can at least quote him
to help to solve the problem :)
Cheers,
--
caio[1982] begotti
http://caio.ueberalles.net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | lothar.behrens@lollisoft.de | 2006-12-12 20:25:53 | Re: SQLSetPos problem ? |
| Previous Message | Tom Lane | 2006-12-12 17:11:11 | Re: possible odbc driver bug with postgresql-7.4 |