On Feb 17, 2008, at 10:41 PM, Chris wrote:
> Chris wrote:
>>> I'm just toying around, so this isn't high priority. I'll probably
>>> change the name of the enum to fielding_position for clarity's sake
>>> anyway. But for my own education - what's so unique about the name
>>> 'position'?
>> It's a string manipulation function:
>> http://www.postgresql.org/docs/8.3/interactive/functions-string.html
If the issue were simply that it were a function name, than I would
have expected that attempting to create an enum type of 'abs' to also
result in a quoted type. That didn't happen, and I stated so in my
initial e-mail.
> Forgot to say, you can see a list of reserved words in the manual too:
>
> http://www.postgresql.org/docs/8.3/interactive/sql-keywords-
> appendix.html
>
> and it's reserved there too.
Yup. Saw that about 3 minutes after I sent the original question. I
sent a follow-up covering that. What I didn't state in that e-mail was
that I tried to create an enum type that was another name in the list
which was non-reserved (cannot be function or type). In that case, I
did see the automatic quoting behavior I saw with position.
Thanks for the prompt reply.
Tim Hart
