Andy Burns wrote:
Christopher A. Watford wrote:
Why anyone would use non lowercase column/field names is beyond me.
I suppose it also caters for using reserved names as column names too,
column names of date/time or similar seem to catch several folks out
upper case is the SQL standard .. but in the php world its common to use
lower case. pgsql for some reason also forces field names to lower case
in assoc fetches. however in MDB2 you can determine which case you want
. native, lower case, upper case ..
I think it was added to the spec merely to support MSSQL's "feature"
which was a relic of Access. I was also under the impression that
EVERY major DB supported standard backtick quoted table/field names
postgres doesn't seem to like it, when I installed RC over the weekend I
had to change all the ` in PHP to \" to get " instead
thats why you want to use quote() and quoteIdentifer() in MDB2
and we all know they support all lowercase field/table names, so I see
this as an issue not with prepared queries but with people being too
db-centric, as you have pointed out.
agreed, but using prepared statements (in the contextr of a web
front-end) is more about protecting yourself from malicious users
crafting "naughty" urls ...
yeah .. the performance improvement is probably not going to be
significant .. especially if most people are using ext/mysql as their
backend, where native prepare statements are not available.
regards,
Lukas
