Don't trigger changes if nothing was actually changed
See original GitHub issueoldDoc not passing
Items.find().observe({
changed(newDoc, oldDoc) {
console.log(newDoc, oldDoc) // { foo: "bar" } undefined
}
})
It’s possbile fix it?
Issue Analytics
- State:
- Created 7 years ago
- Comments:12 (12 by maintainers)
Top Results From Across the Web
make update trigger don't activate with no changing value
To exit the trigger if no rows were affected on SQL Server 2016 and up, Microsoft recommends using the built-in ROWCOUNT_BIG() function in...
Read more >In a trigger, how to check if no fields have changed?
Put this as the very first line in your trigger: -- Exit trigger if no data was actually modified IF (@@ROWCOUNT = 0)...
Read more >manually created 'change' events via new Event() don't trigger ...
My expectation is just that a manually created change event would cause a react change event and that an onChange listener on some...
Read more >If Your Trigger Uses UPDATE(), It's Probably Broken.
No, it really *does* update every row — logically. What it does or does not do physically is entirely irrelevant. The “rows affected”...
Read more >Configure pipeline triggers - Azure - Microsoft Learn
For instance, there is no way to trigger a pipeline on the same branch as that of the triggering pipeline using build completion...
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
Fixed.
@Maxpain177 good find. yes it will be fixed.