-
Notifications
You must be signed in to change notification settings - Fork 13
New feature : enclose names #7
Comments
Hello :-), Here is our position. SQL is a language, with reserved keywords. The user must not use a reserved keywords in its schema, in order to not being in conflict with the SQL language. Nevertheless, if a study shows that one of few common patterns/workarounds exist and are simple to implement, we can review our position. Please, motivate it on the mailing-lists or IRC if you think it is needed. Thoughts? |
@Hywan +1 I'm writing SQL queries everyday on MySQL, PostgreSQL, SQL Anywhere and I never enclose my field names because my databases schemas don't include reserved keywords. |
The feature is not "allow to use keyword as identifier", but enclose identifiers. Sorry :-/ |
@guiled: Why “sorry” :-)? Does enclose identifiers is different as using keywords as identifiers? Maybe we miss something? |
… or, we could enclose names each time, and the symbol would be parameterizable (e.g. |
I have made lot of mistake in this issue like "not having talked about it before" and forget to precise my thoughts. |
This idea is like you purpose so : a method called setEnclosedSymbol($openSymbol, $closeSymbol = null) that will make all identifier (table name, column name, aliases) in a SQL enclosed between symbols. This is not a prior critic feature. |
ping? What is the state of this issue? |
Is it possible to think about the name enclosing in SQL?
Mysql can use
name
Oracle uses "name"
SQL Server handles names like [this]
...
A good topic :
http://stackoverflow.com/questions/10573922/what-does-the-sql-standard-say-about-usage-of-backtick
The text was updated successfully, but these errors were encountered: