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

Re: Access violation (0xC0000005) in PSQLODBC35W.DLL when calling SQLDescribeColW

From: Hiroshi Inoue <inoue(at)tpf(dot)co(dot)jp>
To: Adrien de Croy <adrien(at)qbik(dot)com>
Cc: "pgsql-odbc(at)postgresql(dot)org" <pgsql-odbc(at)postgresql(dot)org>
Subject: Re: Access violation (0xC0000005) in PSQLODBC35W.DLL when calling SQLDescribeColW
Date: 2010-11-10 04:25:06
Message-ID: 4CDA1EA2.3090801@tpf.co.jp (view raw or flat)
Thread:
Lists: pgsql-odbc
(2010/11/10 13:04), Adrien de Croy wrote:
>
> Hi
>
> I have some helper classes to fetch fields from a record, a helper class
> to manage iteration through a result set.
>
> If I call my fetch helper function for some field ordinal it works fine
> the first time. If I call it again (without having called any method to
> change the current row in the result set) it fails on the same ordinal,
> but works on other ordinals.
>
> So, it looks to me like the fetch call is cleaning up the field data
> when you fetch,

If the helper function calls SQLGetData() for the column, yes.
SQLGetData() cleans up data which it returns to the caller and
returns SQL_NO_DATA when all data was returned to the caller.
You can divide into multiple SQLGetData() calls using this feature
when a column has a big data.

regards,
Hiroshi Inoue


In response to

pgsql-odbc by date

Next:From: Silvio BrandaniDate: 2010-11-11 10:49:59
Subject: out of memory query
Previous:From: Adrien de CroyDate: 2010-11-10 04:04:21
Subject: Re: Access violation (0xC0000005) in PSQLODBC35W.DLL when calling SQLDescribeColW

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