From: | "CN LIOU" <cnliou(at)graffiti(dot)net> |
---|---|
To: | pgsql-odbc(at)postgresql(dot)org |
Subject: | Re: IODBC32.DLL: Access Violation |
Date: | 2002-09-25 07:09:47 |
Message-ID: | 20020925070948.17527.qmail@graffiti.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
> > psqlODBC 7.02.0002 + PostgreSql 7.2.1 + Borland BDE + Windows95.
> >
> > ODBC behaves very strangely for bytea:
> >
> > create table MyTable (c1 integer,c2 bytea);
> > --Then fill up value2 with blob value using Borland Delphi.
> > INSERT INTO MyTable VALUES(:value1,:value2)
>
> Are you binding the :value2 as LongVarBinary ?
The answer is "No" if you refer LongVarBinary to Delphi's field type. I want to associate :value2 with Delphi's TBlobField.
If you refer LongVarBinary to the switches in pgsqlODBC, I have just tried switching on/off "Unknowns As LongVarChar" and "Maximum/Longest" in "Unknown sizes" box. They all give me the same result that follows.
> > The inserted row is really odd - c2 contains the OID pointing to
> > the blob data. Though I don't know where the blob data actually
> > reside, lo_export command does export the blob data to Linux file
> > system. The even more serious problem I cannot circumvent is that
> > I don't know how to retrieve that blob data from PostgreSQl through
> > psqlODBC. This is because psqlODBC seems to not be able to return
> > blob field type for BDE.
Best Regards,
CN
--
_______________________________________________
Get your free email from http://www.graffiti.net
Powered by Outblaze
From | Date | Subject | |
---|---|---|---|
Next Message | ggorcsos | 2002-09-25 07:29:48 | ODBC SQL connect problem |
Previous Message | Michael Fox | 2002-09-25 05:33:08 | crystal reports pgSQL ODBC |