Why SELECT keyword on parser is written as SELECTME ?

From: Mohammad Heykal Abdillah <heykal(dot)abdillah(at)gmail(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Why SELECT keyword on parser is written as SELECTME ?
Date: 2010-05-21 03:41:06
Message-ID: 1274413266.19021.20.camel@claudia
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(dot)abdillah(at)gmail(dot)com>

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2010-05-21 03:50:00 Re: Why SELECT keyword on parser is written as SELECTME ?
Previous Message Robert Haas 2010-05-21 03:40:03 Re: [RFC][PATCH]: CRC32 is limiting at COPY/CTAS/INSERT ... SELECT + speeding it up