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
underl
"=?iso-8859-1?Q?H=E9lder_M._Vieira?=" <[EMAIL PROTECTED]> writes:
> If max() operates on a 'varchar' type column, the result appears with 'text'
> type.
> Should I expect this behaviour in the current and later versions ?
This is true of just about everything, not only max() -- there are *no*
fun
Hello.
I'm having some trouble with an unexpected conversion performed by the max()
function.
If max() operates on a 'varchar' type column, the result appears with 'text'
type.
Should I expect this behaviour in the current and later versions ?
I mention this because I'm using ODBC in VB, and
