This PR allows the developer to take responsability of column names and table names correctness,
by correctness I mean no special characters and no postgres reserved keywords.
Benefits :
less run time for checking each byte for an invalid character,
more flexibility when the developer wants to ignore casing in his database columns and table names
User Case Description
In my case, the double quotes around table names and columns, make my query case sensitive to the casing of table names
and columns.
In my case, performance is crucial, avoiding going over bytes in the query, could be significant on the long run
What did this pull request do?
This PR allows the developer to take responsability of column names and table names correctness, by correctness I mean no special characters and no postgres reserved keywords.
Benefits :
less run time for checking each byte for an invalid character,
more flexibility when the developer wants to ignore casing in his database columns and table names
User Case Description
In my case, the double quotes around table names and columns, make my query case sensitive to the casing of table names and columns.
In my case, performance is crucial, avoiding going over bytes in the query, could be significant on the long run