ORcan short circuit the
LIKEstatements in parenthesis. This is done in qb using a function callback to
whencontrol flow function, it was easy to miss this. This is because you are already in a closure - it looks the same as when using
whereto group the clauses.
whenwill automatically group added where clauses when needed. That means our original example now produces the SQL we probably expected.
ORcombinator. In these cases no grouping is added.
whencallback, nothing changes. Your code works as before. The
ORcombinator check only works on the top most level of added where clauses.
whencallback, nothing changes from qb 7.
withoutScopingflag to the
MSSQLGrammarwas visually too close to
MySQLGrammarand was hard to differentiate quickly.
SqlServerGrammaris much more unique and easily identifiable. Additionally, more people that use this library refer to their database engine as "SQL Server" than "MSSQL".
defaultGrammarwas used to look up a mapping in the
@qbnamespace. This made it difficult to add or use grammars that weren't part of qb. (You could get around this be registering your custom grammar in the
@qbnamespace, but doing so seemed strange.)
defaultGrammarto be the full WireBox mapping in your
defaultValueparameter and optional exception throwing was added to
value. This pushed the
optionsstruct to the end of the method. If you are using positional parameters with
value, you will need to update your method calls to either use named parameters or the new positions.
queryin the following cases: