when chaining update calls, only the last takes effect
See original GitHub issueWhereas where
calls can be chained like so:
> knex('foo').where('a', 1).where('b', 2).toString()
'select * from "foo" where "a" = \'1\' and "b" = \'2\''
update
calls cannot:
> knex('foo').update('a', 1).update('b', 2).toString()
'update "foo" set "b" = \'2\''
May not exactly be a bug, but the difference has me wondering whether this is by design.
Issue Analytics
- State:
- Created 9 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Trouble chaining useEffects to use updated state from ...
I don't see it as a dependency since it's not referenced in the hook callback. When currentUser changes it will trigger both effects...
Read more >Promises chaining - The Modern JavaScript Tutorial
Here the first .then shows 1 and returns new Promise(…) in the line (*) . After one second it resolves, and the result...
Read more >Optional chaining (?.) - JavaScript - MDN Web Docs - Mozilla
The optional chaining (?.) operator accesses an object's property or calls a function. If the object accessed or function called is ...
Read more >Injecting side effects into chained Sequence operations
When you call a method like map on a value that conforms to LazySequenceProtocol , the compiler will favor the lazy variant of...
Read more >Constructor Chaining In Java with Examples - GeeksforGeeks
Constructor chaining is the process of calling one constructor from another constructor with respect to current object.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@rhys-vdw @wubzz Any update on this?
Seems like in PR #1437 there is problem to implement the chaining
insert
but it seems that there is no problem with the chainingincrement
. Any chance to add at least the chainingincrement
? Or is there a workaroud that avoid to make X separate queries for incrementing x fields?