Why SELECT keyword on parser is written as SELECTME ?

Поиск
Список
Период
Сортировка
От Mohammad Heykal Abdillah
Тема Why SELECT keyword on parser is written as SELECTME ?
Дата
Msg-id 1274413266.19021.20.camel@claudia
обсуждение исходный текст
Ответы Re: Why SELECT keyword on parser is written as SELECTME ?  (Robert Haas <robertmhaas@gmail.com>)
Список 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 по дате отправления:

Предыдущее
От: Robert Haas
Дата:
Сообщение: Re: [RFC][PATCH]: CRC32 is limiting at COPY/CTAS/INSERT ... SELECT + speeding it up
Следующее
От: Robert Haas
Дата:
Сообщение: Re: Why SELECT keyword on parser is written as SELECTME ?