Whats the techy term for a situation where...
In an ORstatement it will stop checking when it hits something thats true, where as in an AND it will stop checking the conditions when it hits something that is false?
It's obviously some optimisation stuff (i.e. put the stuff you think it most likely to fail first)... but can't for the life of me remember! I know C# does this, but guy at work said SQL doesnt - but I think it does!
Cheers
In an ORstatement it will stop checking when it hits something thats true, where as in an AND it will stop checking the conditions when it hits something that is false?
It's obviously some optimisation stuff (i.e. put the stuff you think it most likely to fail first)... but can't for the life of me remember! I know C# does this, but guy at work said SQL doesnt - but I think it does!
Cheers
