From: Hiroshi Inoue <Inoue@tpf.co.jp>
To: markMLl.pgsql-interfaces@telemetry.co.uk
Cc: pgsql-interfaces@PostgreSQL.org, "pgsql-odbc@postgresql.org" <pgsql-odbc@PostgreSQL.org>
Subject: Re: Getting info on "Max LongVarChar" under ODBC
Date: Tue, 10 Jul 2001 08:03:57 +0900
Message-ID: <3B4A385D.D5C49354@tpf.co.jp> (raw)
References: <3B4845AF.D933DD72@telemetry.co.uk>
<3B48F43E.45A63C9B@tpf.co.jp>
<3B4996ED.363BBEE4@telemetry.co.uk>
markMLl.pgsql-interfaces@telemetry.co.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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: Inoue@tpf.co.jp, markMLl.pgsql-interfaces@telemetry.co.uk, pgsql-odbc@PostgreSQL.org
Subject: Re: Getting info on "Max LongVarChar" under ODBC
In-Reply-To: <3B4A385D.D5C49354@tpf.co.jp>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox