Neil Conway <[EMAIL PROTECTED]> writes:
> On Tue, 2008-01-29 at 13:20 -0500, Tom Lane wrote:
>> The reason it was kept was to override the search path --- unqualified
>> NUMERIC will always be taken as pg_catalog.numeric even if you have some
>> other type "numeric" in front of it.

> It should be possible to implement this behavior without requiring
> NUMERIC to be a keyword, though.

Perhaps we could find some other, even uglier kludge ... I doubt it
would be an improvement.  Is there any particular reason NUMERIC
*shouldn't* be a keyword?  It's called out as a <reserved word> by
the spec, after all.  (In fact, I seem to recall that it was exactly
that point that made us decide that the implicit conversion to
pg_catalog.numeric was appropriate.)

                        regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

Reply via email to