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

Re: Getting info on "Max LongVarChar" under ODBC

From: Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>
To: markMLl(dot)pgsql-interfaces(at)telemetry(dot)co(dot)uk
Cc: pgsql-interfaces(at)PostgreSQL(dot)org, "pgsql-odbc(at)postgresql(dot)org" <pgsql-odbc(at)PostgreSQL(dot)org>
Subject: Re: Getting info on "Max LongVarChar" under ODBC
Date: 2001-07-09 23:03:57
Message-ID: 3B4A385D.D5C49354@tpf.co.jp (view raw or flat)
Thread:
Lists: pgsql-interfacespgsql-odbc
markMLl(dot)pgsql-interfaces(at)telemetry(dot)co(dot)uk wrote:
> 
> Hiroshi Inoue wrote:
> 
> > You seem to be able to call SQLGetTypeInfo() though
> > I'm not sure.
> 
> Many thanks, I obviously need to work out on ODBC programming :-) At
> present I'm doing a temporary job by querying the parameter from the
> registry- but that will obviously fail if I need to look at an
> alternative database.
> 
> However, I've now found that even if I change the Max LongVarChar
> parameter from its default 8190 to (say) 16382 an attempt to save more
> than 8K text still gets truncated. I can work around this for the time
> being but would appreciate it if anybody could tell me whether there are
> still any outstatding issues.
> 

Please try the latest driver(7.01.0006).
It removed the text/query length limit.

regards,
Hiroshi Inoue

In response to

Responses

pgsql-odbc by date

Next:From: Henshall, Stuart - WCPDate: 2001-07-10 09:38:05
Subject: RE: [NOVICE] Trouble with pg_hba.conf and Access.
Previous:From: Neal LindsayDate: 2001-07-09 20:07:51
Subject: Re: [NOVICE] Trouble with pg_hba.conf and Access.

pgsql-interfaces by date

Next:From: Barry LindDate: 2001-07-10 01:21:54
Subject: Re: Too much data received?
Previous:From: Steve WamplerDate: 2001-07-09 17:27:28
Subject: Re: Too much data received?

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