The order of condition expressions in SQL queries?

Question

4.67/5 (3 votes)

See more:

I know the order of conditions is important in at least C and C#. For example, the two following conditions are different:
1. (str1.Length > 0&&str1[0] == 'A')
This works well and is the correct one.
2. (str1[0] == 'A'&&str1.Length>0)
This is too ridiculous because the order of executing commands (in this case) is from left to right, if str1.Length = 0, an exception will be thrown, so it can't work. This is only a simple example. But what I want to know is Do SQL queries work the same way with conditions after WHERE, HAVING, ON or anywhere else possible?
Thank you so much!

Posted 18-Apr-11 20:59pm

King Boy

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Accepted Answer · 2011-04-18T21:11:00

Do you want the bad news? Sorry, but SQL does not behave the same as C, C++ and C#. In those, AND clauses are always executed left - to right, and any false result will abort the operation (called "evaluation short-circuiting"). SQL does not do that. What it does do is more complex. There is a description here: How SQL Server short circuits WHERE condition evaluation[^]

Gets my five for a very good question, though!