Bug #6659 for SQL-Statement: SQL::Parser do not treat fiedls starting with undescores as valid table fields

Thu Jun 17 21:00:15 2004 Guest - Ticket created

Subject:

SQL::Parser do not treat fiedls starting with undescores as valid table fields

distribution: SQL-Statement-1.09 SQL::Parser do not treat fiedls starting with undescores as valid table fields. In sub. SQL::Parser::IDENTIFIER this case was called as "BAD START".

Thu Jun 17 21:13:12 2004 JZUCKER [...] cpan.org - Correspondence added

Show quoted text

> SQL::Parser do not treat fiedls starting with undescores as valid table

That's the ANSI SQL standard - identifiers must begin with a-z or A-Z, they can not start with underscore or numbers. If you want to use a non-standard table name, you need to use Identifier delimiters - put quotes around the name e.g. #1 is valid SQL and accepted by SQL::Parser, but #2 is invalid SQL and rejected by SQL::Parser 1. SELECT * FROM "_mytable" 2. SELECT * FROM _mytable In the future I may allow "loosening" SQL rules (allow names that are not valid ANSI SQL). Thanks for your report!

Thu Jun 17 21:13:13 2004 JZUCKER [...] cpan.org - Status changed from 'new' to 'resolved'

Thu Jun 17 21:13:13 2004 JZUCKER [...] cpan.org - Given to JZUCKER

Thu Jun 17 21:49:58 2004 Guest - Correspondence added

[JZUCKER - Thu Jun 17 21:13:12 2004]: Show quoted text

> > SQL::Parser do not treat fiedls starting with undescores as valid

> table > > That's the ANSI SQL standard - identifiers must begin with a-z or A-Z, > they can not start with underscore or numbers. If you want to use a > non-standard table name, you need to use Identifier delimiters - put > quotes around the name e.g. #1 is valid SQL and accepted by > SQL::Parser, > but #2 is invalid SQL and rejected by SQL::Parser > > 1. SELECT * FROM "_mytable" > 2. SELECT * FROM _mytable > > In the future I may allow "loosening" SQL rules (allow names that are > not valid ANSI SQL). > > Thanks for your report!

Thank you for your reply. I did'nt mean undescores in table name, but I mean column names. I may be wrong, but I often use columns beginning from undescores and never got any problems before. Thanks again for you reply. Andrew.

Thu Jun 17 21:49:59 2004 The RT System itself - Status changed from 'resolved' to 'open'

Sun Feb 27 13:52:26 2005 JZUCKER [...] cpan.org - Correspondence added

Rules for SQL Identifiers apply to both table and column names. If you want to start one with an underscore, you must delimit it with quotes to be valid

Sun Feb 27 13:52:26 2005 JZUCKER [...] cpan.org - Status changed from 'open' to 'resolved'