Re: BUG: text(varchar) truncates at 31 bytes

From: Thomas Lockhart <lockhart(at)fourpalms(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com>, Dave Blasby <dblasby(at)refractions(dot)net>, thomas pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: BUG: text(varchar) truncates at 31 bytes
Date: 2001-10-03 23:38:47
Message-ID: 3BBBA187.6ABAE7BB@fourpalms.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

...
> Perhaps it'd be a better idea for the option of a freebie conversion
> to be checked earlier, say immediately after we discover there is no
> exact match for the function name and input type. Thomas, what do you
> think?

We *really* need that catalog lookup first. Otherwise, we will never be
able to override the hardcoded compatibility assumptions in that
matching routine. Once we push that routine into a system catalog, we'll
have more flexibility to tune things after the fact.

Without the explicit function call, things would work just fine for the
example at hand, right?

I could put in a dummy passthrough routine. But that seems a bit ugly.

- Thomas

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message John Summerfield 2001-10-03 23:53:43 Re: cvs problem
Previous Message John Summerfield 2001-10-03 23:36:15 Re: CVS changes