Feature: add bulk_save to HistoryModel

[weilu]

This allows for efficient update and create of multiple instances based on 'id' field – those without supplied id values are created, otherwise updated.
All operations are atomic - either all succeed or all fail.

Unit tests in social_protection module due to dependency requirements

[Copilot]

Pull Request Overview

This PR adds a bulk_save class method to the HistoryModel for efficiently creating and updating multiple instances in a single atomic transaction. Instances without an id are created, while those with an id are updated.

• Adds bulk_save class method supporting batch operations with configurable batch size
• Implements atomic transaction handling to ensure all-or-nothing semantics
• Handles version tracking and timestamp management for both create and update operations

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Accessing to_update[0] without checking if to_update is empty will raise an IndexError. This code is inside the if to_update: block but relies on at least one element existing. While the if to_update: check prevents the block from executing when empty, the logic assumes all instances have identical field sets, which may not hold if the model has fields with null=True or if different subclasses are mixed. Consider extracting field names from the model's _meta.get_fields() instead of relying on instance __dict__.

Suggested change

	update_fields = [f for f in to_update[0].__dict__.keys()
	if not f.startswith('_') and f not in exclude_fields]
	update_fields = [
	field.name for field in cls._meta.get_fields()
	if (
	field.concrete
	and not field.auto_created
	and not (field.many_to_many or field.one_to_many)
	and field.name not in exclude_fields
	)
	]

[Copilot]

Using F('version') + 1 with bulk_update will not work as expected. The F expression is meant for database-level updates in .update() calls, but bulk_update saves the current Python object values to the database. The F expression will be serialized as-is rather than being evaluated as SQL. This will either fail or set an incorrect value. The version increment logic at lines 288-292 attempts to compensate by re-fetching versions, but the initial assignment is still problematic. Set instance.version to the current value + 1 instead: instance.version = instance.version + 1.

Suggested change

	instance.version = F('version') + 1
	instance.version = instance.version + 1

[delcroip]

@weilu can you double check that ?

[weilu]

I don't think the use of F('version') itself is problematic as proven by passing unit test in openimis/openimis-be-social_protection_py#119, but we can switch to instance.version for clarity

[delcroip]

can it be default at None and retrieve it from the get_current_user() ?

[weilu]

Models shouldn't be aware of current user as that's at the controller layer.