Hey, yes there is now `Convert::symbol2sql`, which does a database-specific identifier escape. The problem is that the framework is effectively built around the ANSI SQL convention that DB identifiers are double quoted. In order to remain as consistent as possible, and to limit any potential breaking changes, I've opted to maintain the standard double quote practice within the framework. This new method is mostly used as a secondary or fallback quoting mechanism (such as in `SQLExpression::renameTable`).

To be honest, I'm doubtful of it's use, since ANSI SQL is good enough for any framework or user code. The choice to implement this was more a case of it being easy to write, and a seemingly obvious function where a standard database behaviour could be abstracted. We could probably drop this method and maintain the current convention.