[HACKERS] Why SELECT keyword on parser is written as SELECTME ?
in [PgSql]
|
Prev: [RFC][PATCH]: CRC32 is limiting at COPY/CTAS/INSERT ... SELECT + speeding it up
Next: Why SELECT keyword on parser is written as SELECTME ?
From: Mohammad Heykal Abdillah on 20 May 2010 23:41 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(a)gmail.com> -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers |