Skip site navigation (1) Skip section navigation (2)

Re: IODBC32.DLL: Access Violation

From: Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>
To: CN LIOU <cnliou(at)graffiti(dot)net>
Cc: pgsql-odbc(at)postgresql(dot)org
Subject: Re: IODBC32.DLL: Access Violation
Date: 2002-09-25 00:31:09
Message-ID: 3D9103CD.FC657C1B@tpf.co.jp (view raw, whole thread or download thread mbox)
Thread:
Lists: pgsql-odbc
CN LIOU wrote:
> 
> Hi!
> 
> 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 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.
> 
> Thus, I am trying to use TEXT column instead - and fail, too:
> 
> create table MyTable (c1 integer,c2 text);
> --Then fill up value2 with string value using Delphi.
> INSERT INTO MyTable VALUES(:value1,:value2)
> 
> The INSERT results in Access Violation from IODBC32.DLL.
> Please note that value2 is about 55 kbytes in size and contains
> some low values, '\0' in terms of C. Can this be the problem
> confusing pgsqlODBC?

Yes.
 
regards,
Hiroshi Inoue
	http://w2422.nsk.ne.jp/~inoue/

In response to

pgsql-odbc by date

Next:From: Keith GrayDate: 2002-09-25 00:42:52
Subject: Timestamp Error
Previous:From: Hiroshi InoueDate: 2002-09-24 23:55:28
Subject: Re: Timestamp Error

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group