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

RE: Truncation Problems

From: "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Jeremy D Carlson" <jeremy(at)gustavus(dot)edu>
Cc: <pgsql-bugs(at)postgresql(dot)org>
Subject: RE: Truncation Problems
Date: 2001-06-23 02:53:33
Message-ID: EKEJJICOHDIEMGPNIFIJMEBHEMAA.Inoue@tpf.co.jp (view raw or flat)
Thread:
Lists: pgsql-bugs
> -----Original Message-----
> From: Tom Lane
>
> Jeremy D Carlson <jeremy(at)gustavus(dot)edu> writes:
> > We are having problems with information we are inserting into our
> > database being truncated.  This information is being inserted via the
> > web through Apache 1.3.6 while using ColdFusion 4.0.1's ODBC interface
> > into a PostgreSQL 7.0.2 database.  It is being truncated in a couple of
> > ways.  Sometimes, after so many characters, the information is truncated
> > in each column.  Other times, the information for the last part of the
> > insertion string is lost.  These insertions usually contain a couple
> > paragraphs of information for each column.  We haven't had any problem
> > with short insertions.  Neither ColdFusion nor PostgreSQL return an
> > error on a truncation.  We occasionally will receive a "query string too
> > long" error from PostgreSQL, but no information is actually inserted
> > into the database.  The query string error is also confusing because
> > each column should be able to contain 1+GBs of information.
>
> 7.0.2 does not support "1+GBs" per column.  You need to update to 7.1.*
> to have wide columns.
>
> The error message "query string too long" is also suspicious, since that
> string appears nowhere in either current or 7.0 sources.

The message seems to come from ODBC driver. It has the query length
limit 65536. The new driver which would be released in a week or so has
no query length limit.
As for truncation, there could be some causes.
1) PostgreSQL silently truncates the text.
2) Psqlodbc driver increases the text size by converting '\n' -> CR/LF
   and the buffer overflows. Unfortunately SQL(Extended)Fetch returns
   an SQL_SUCCESS_WITH_INFO not an SQL_ERROR in suc cases.

regards,
Hiroshi Inoue


In response to

pgsql-bugs by date

Next:From: dkleeDate: 2001-06-23 14:50:45
Subject: How to acces BLOB field in postgres with JAVA ?
Previous:From: Lotus Luby-LooDate: 2001-06-22 15:59:08
Subject: Strange security behaviour!

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