From: Hélder M. Vieira <hmv@mail.telepac.pt>
To: pgsql-sql@postgresql.org
Subject: Re: max() unexpected type conversion
Date: Tue, 22 Nov 2005 01:40:00 -0000
Message-ID: <002a01c5ef05$da3bbc30$6200a8c0@hmv02> (raw)
References: <000901c5ee99$c275e380$580bfea9@hmv02>
<1719.1132585425@sss.pgh.pa.us>
> This is true of just about everything, not only max() -- there are *no*
> functions yielding varchar in recent PG releases
Thanks for the information. I added an explicit cast to the max() output and
it works fine.
Anyway, for those using VB, this is potentially hazardous. Knowing that the
underlying data is of type 'varchar', one has to be always very cautious
about the 'text' conversion, otherwise all readings after the first will
return null instead of valid data.
Helder M. Vieira
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-sql@postgresql.org
Cc: hmv@mail.telepac.pt
Subject: Re: max() unexpected type conversion
In-Reply-To: <002a01c5ef05$da3bbc30$6200a8c0@hmv02>
* 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