# 459 Problems When Using Field Names As Constants in SQL Queries

---

It is my impression that the SQL statement
Where ('fName' = 'blue')
is ambiguous (in that 'fName' and/or 'blue' could be either a field or a literal). Thus, if a user accidentally has a field value of 'blue' for the field 'fName', and if there is another field named 'blue', then the SQL might not behave the way the user would wish: the SQL might compare the values of the
two fields, and not a field vs a literal. The issue seems to be that statements like 'field = literal' should behave correctly independent of the names of the other fields. SQL which worked 'correctly' on Monday, might start misbehaving simply because the developer added a field named 'blue'.