pg.ddx.io  pgsql-interfaces@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: markMLl.pgsql-interfaces@telemetry.co.uk
To: pgsql-interfaces@PostgreSQL.org
Subject: Re: Getting info on "Max LongVarChar" under ODBC
Date: Mon, 09 Jul 2001 11:35:09 +0000
Message-ID: <3B4996ED.363BBEE4@telemetry.co.uk> (raw)
References: <3B4845AF.D933DD72@telemetry.co.uk>
	<3B48F43E.45A63C9B@tpf.co.jp>

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.

Hope this isn't an FAQ but I've not found it yet.

Running 7.1.2, I've got a table which amongst other things has a field
declared as TEXT into which I'm saving a script for interpretation on
the client system. On the ODBC driver settings I've got "Unknown Sizes"
as "Longest", "Text as LongVarChar" enabled, and "Max LongVarChar" set
to 16382. I've rebooted after changing the parameters in case they were
only read when the driver was loaded. Client OS is NTW4SP3, ODBC driver
Insight 7.01.0005.

-- 
Mark Morgan Lloyd
markMLl .AT. telemetry.co .DOT. uk

[Opinions above are the author's, not those of his employers or
colleagues]



view thread (5+ messages)  latest in thread

Message-ID: <3B4996ED.363BBEE4@telemetry.co.uk>
Permalink:  ../3B4996ED.363BBEE4@telemetry.co.uk/
Also on:    postgresql.org/message-id/3B4996ED.363BBEE4@telemetry.co.uk

 · 

reply

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: markMLl.pgsql-interfaces@telemetry.co.uk
  Subject: Re: Getting info on "Max LongVarChar" under ODBC
  In-Reply-To: <3B4996ED.363BBEE4@telemetry.co.uk>

* 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