On Feb 18, 2008, at 12:10 AM, Tom Lane wrote:
Would it have been reasonable to expect some kind of notice or warning
message stating that 'position' was special, and
position would be used instead?
The way you phrase that makes me think you misunderstand what's
happening here. The name of th
Tim Hart <[EMAIL PROTECTED]> writes:
> At the time I executed the statement
> create type position as enum('pitcher', 'catcher', 'first base',
> 'second base', 'third base', 'short stop', 'left field', 'center
> field', 'right field', 'designated hitter', 'pinch hitter');
> Would it have been r
On Feb 17, 2008, at 11:21 PM, Tom Lane wrote:
The reason "position" is special is that the SQL spec calls out weird
specialized syntax for it:
Given the spec, I completely understand.
Given the roundabout way I discovered the nature of the problem, I'm
curious:
At the time I executed the
Tim Hart <[EMAIL PROTECTED]> writes:
> On Feb 17, 2008, at 10:41 PM, Chris wrote:
> 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
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 mani
On Feb 17, 2008, at 21:24 , Tim Hart wrote:
But for my own education - what's so unique about the name 'position'?
It's an SQL keyword:
http://www.postgresql.org/docs/8.3/interactive/sql-keywords-
appendix.html
Michael Glaesemann
grzm seespotcode net
---(end of
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/
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/inter
