SQL Statement Stitching technique (reduces program bloat due to judging conditions)

A fixed SQL we can spell this: SELECT * from Lccont where ID < $ ORDER by ID, but what if we don't know the criteria for the query?

If each condition is changed to determine whether the first condition is too bloated for the program, we can spell the fixed section of SQL as: "SELECT * from Lccont where 1=1", so that we can directly append "and ID < 1000" on the back. Query conditions resolved, if the sorting conditions are not clear?

We can spell the fixed section of SQL as: "SELECT * from Lccont where 1= 1 order 1=1" so we just need to append ", id" on the back.

Using this method to reduce repetitive and meaningless judgments can make the structure of the program clearer.

SQL Statement Stitching technique (reduces program bloat due to judging conditions)