Why SELECT keyword on parser is written as SELECTME ? - Mailing list pgsql-hackers

From Mohammad Heykal Abdillah
Subject Why SELECT keyword on parser is written as SELECTME ?
Date
Msg-id 1274413266.19021.20.camel@claudia
Whole thread Raw
Responses Re: Why SELECT keyword on parser is written as SELECTME ?
List pgsql-hackers
All,

I was trying to implement some database language into PostgreSQL. Let's
say an SQL command that using local language as it's command. I know
it's not standard, but it's not the issue for me.

I made a lot modification in "scan.l" and "gram.y" and related file in
parser (src/backend/parser). So far my modified code was compiled well,
and PostgreSQL can run normaly, of course without ability to use SQL
command to Database, but it can check validty of SQL command structure.

After i modified the parser, compile and running PostgreSQL. My modified
PostgreSQL, identified "select" keyword as invalid keyword but
"selectme" keyword is valid.

Using unmodified PostgreSQL, "select" keyword was valid but "selectme"
keyword was invalid.

I just wonder why "select" keyword token in PostgreSQL is identified as
"selectme" (at src/backend/parser/keywords.c)?

Whats it's the different between "select" and "selectme" ?

Thank You.


-- 
Mohammad Heykal Abdillah <heykal.abdillah@gmail.com>




pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [RFC][PATCH]: CRC32 is limiting at COPY/CTAS/INSERT ... SELECT + speeding it up
Next
From: Robert Haas
Date:
Subject: Re: Why SELECT keyword on parser is written as SELECTME ?