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

Re: SQLExecute fails question

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: Tomas Skäre <tomas(at)nocrew(dot)org>
Cc: <pgsql-odbc(at)postgresql(dot)org>
Subject: Re: SQLExecute fails question
Date: 2004-07-21 10:31:37
Message-ID: E7F85A1B5FF8D44C8A1AF6885BC9A0E41A73AF@ratbert.vale-housing.co.uk (view raw or flat)
Thread:
Lists: pgsql-odbc
 

> -----Original Message-----
> From: Tomas Skare [mailto:tomas(at)junk(dot)nocrew(dot)org] On Behalf Of 
> Tomas Skäre
> Sent: 21 July 2004 11:23
> To: Dave Page
> Cc: pgsql-odbc(at)postgresql(dot)org
> Subject: Re: [ODBC] SQLExecute fails question
> 
> "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> writes:
> 
> > > [mailto:pgsql-odbc-owner(at)postgresql(dot)org] On Behalf Of Joost 
> > > Kraaijeveld
> > > 
> > > Hi all,
> > > 
> > > When I get this error message from a SQLExecute():
> > > 
> > > [2152] SQLSTATE = HY000
> > > [2152] Native rc Code = 7
> > > [2152] Message: ERROR:  value too long for type character(20)
> > > 
> > > does that mean that one of my columns as that is defined as
> > > char(20) receives more data than 20 chars or does that mean that 
> > > column 20 receives to many chars?
> > 
> > The first. The data is too long for char(20).
> 
> It would be very helpful sometimes to know what column that 
> failed. But maybe that's really a PostgreSQL issue, and not 
> the ODBC driver?

Yes it is.

Regards, Dave.

pgsql-odbc by date

Next:From: Theodore PetroskyDate: 2004-07-21 14:22:50
Subject: Re: 07.05.0001 Snapshot available
Previous:From: Tomas =?iso-8859-1?q?Sk=E4re?=Date: 2004-07-21 10:22:54
Subject: Re: SQLExecute fails question

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