Re: BUG: text(varchar) truncates at 31 bytes
| От | Thomas Lockhart |
|---|---|
| Тема | Re: BUG: text(varchar) truncates at 31 bytes |
| Дата | |
| Msg-id | 3BBBA187.6ABAE7BB@fourpalms.org обсуждение исходный текст |
| Ответ на | Re: BUG: text(varchar) truncates at 31 bytes (Stephan Szabo <sszabo@megazone23.bigpanda.com>) |
| Ответы |
Re: BUG: text(varchar) truncates at 31 bytes
|
| Список | 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
В списке pgsql-hackers по дате отправления: