Re: Call for objections: revision of keyword classification

Tom Lane writes:

> ColId is certainly the most important category for ordinary users, so
> I agree that division would be sufficient for most people's purposes.
> However ... seems like the point of having this documentation at all
> is for it to be complete and accurate.  I'd vote for telling the whole
> truth, I think.

Okay, here's the new definition of truth then:

TypeFuncId => "non-reserved"
ColId      => "non-reserved (cannot be function or type)"
func_name  => "reserved (can be function)"
ColId      => "reserved"

This can still be matched well against the SQL 9x columns.

But it gets worse... ;-)

I found that COALESCE, EXISTS, EXTRACT, NULLIF, POSITION, SUBSTRING, TRIM
can be moved from ColLabel to ColId.  (This makes sense given the new
definition of ColId as above.)  However, I *think* it should be possible
to use these tokens as type names if one were willing to refactor these
lists further.  So there's possibly plenty of fun left in this area. ;-)

-- 
Peter Eisentraut   peter_e@gmx.net