Why Developers Use “WHERE 1=1” in SQL Queries

Programmers often encounter the pattern WHERE 1=1 in SQL statements and wonder why it is used. Although the query result is identical to omitting the clause, the purpose is not to change the result but to provide a convenient true condition.

SQL Injection Context

When constructing queries that may later be combined with OR conditions, 1=1 ensures the expression remains true, which can be exploited in injection attacks. For example, adding OR 1=1 to a delete statement will delete all rows instead of only the intended ones.

Dynamic Query Building and Syntax Safety

In application code, developers often build SQL strings conditionally. Starting the WHERE clause with 1=1 allows subsequent AND fragments to be appended without worrying about whether a preceding condition exists. Without the placeholder, a generated query like SELECT * FROM table_name WHERE AND var2=value2 would be syntactically invalid.

String sql = "select * from table_name where 1=1";
if (condition1) { sql = sql + " and var2=value2"; }
if (condition2) { sql = sql + " and var3=value3"; }

If both conditions are true, the final query becomes

SELECT * FROM table_name WHERE 1=1 AND var2=value2 AND var3=value3

, which is valid. The placeholder eliminates the need for complex conditional logic to insert the WHERE keyword only when needed.

Table Copying and Backup Scenarios

When copying a table or creating a backup, developers may write:

CREATE TABLE new_table AS SELECT * FROM source_table WHERE 1=1;

This copies all rows. To copy only the structure without data, a false condition such as WHERE 1<>1 can be used, guaranteeing that no rows satisfy the filter.

Performance Considerations

In early MySQL versions, the literal WHERE 1=1 could prevent the optimizer from using indexes, forcing a full table scan and degrading performance on large tables. Since MySQL 5.6 (and possibly earlier), the optimizer recognizes and removes the redundant true condition, so it no longer impacts query speed.

Conclusion

Using WHERE 1=1 is a practical technique for simplifying dynamic SQL generation, avoiding syntax errors, and facilitating table copying. While it once had performance drawbacks in older MySQL releases, modern versions handle it efficiently, making it a safe placeholder in most scenarios.