Tech
NocoBase updates by primary key, not by your filter
If you have used Django, you know there are two ways to update many rows, and you pick one on purpose.
QuerySet.update() sends one SQL statement. It does not call save() , and it does not emit pre_save or post_save . Looping over objects and calling Model.save() does the opposite: one statement per row, signals fire, and it is slower. Neither is always right. You choose based on whether anything is listening.
NocoBase does not offer that choice. Every filtered bulk update goes th...
Read the full discussion on Dev.to
This article was aggregated from Dev.to. Click to join the conversation.
View on Dev.to