Received: from sd.tpf.co.jp (sd.tpf.co.jp [210.161.239.34]) by postgresql.org (8.11.3/8.11.1) with SMTP id f69N2la12099 for ; Mon, 9 Jul 2001 19:02:47 -0400 (EDT) (envelope-from Inoue@tpf.co.jp) Received: (qmail 26460 invoked from network); 9 Jul 2001 23:02:42 -0000 Received: from unknown (HELO viscomail.tpf.co.jp) (100.0.0.108) by sd2.tpf-fw-c.co.jp with SMTP; 9 Jul 2001 23:02:42 -0000 Received: from tpf.co.jp ([126.0.1.68]) by viscomail.tpf.co.jp (8.8.8+Sun/8.8.8) with ESMTP id IAA09747; Tue, 10 Jul 2001 08:02:40 +0900 (JST) Message-ID: <3B4A385D.D5C49354@tpf.co.jp> Date: Tue, 10 Jul 2001 08:03:57 +0900 From: Hiroshi Inoue X-Mailer: Mozilla 4.73 [ja] (Windows NT 5.0; U) X-Accept-Language: ja MIME-Version: 1.0 To: markMLl.pgsql-interfaces@telemetry.co.uk CC: pgsql-interfaces@PostgreSQL.org, "pgsql-odbc@postgresql.org" Subject: Re: Getting info on "Max LongVarChar" under ODBC References: <3B4845AF.D933DD72@telemetry.co.uk> <3B48F43E.45A63C9B@tpf.co.jp> <3B4996ED.363BBEE4@telemetry.co.uk> Content-Type: text/plain; charset=iso-2022-jp Content-Transfer-Encoding: 7bit X-Archive-Number: 200107/40 X-Sequence-Number: 1793 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