Django中使用Concat更新TextField后，如何正确处理log字段？

Let's break down your problem first: when you assign a Concat object directly to self.log and call save(), that expression sticks around on your model instance. The next time you call save()—even if you're only updating message—Django will re-run that Concat logic, leading to duplicated log entries. And using refresh_from_db() kills the performance gain you got from using Concat in the first place.

Here's the cleanest fix that keeps the performance boost and avoids duplicates:

Use QuerySet.update() Instead of Instance.save() #

Instead of assigning the Concat expression to your model instance's field, use Django's QuerySet.update() method to run the database-level update directly. This way, you never store the Concat object on your instance, so there's no chance of it being re-executed later.

Here's your updated update method:

from django.db.models.functions import Concat
from django.db.models import Value

def update(self, log=None, message=None):
    updates = {}
    
    # Gather all fields we need to update
    if log is not None:
        updates['log'] = Concat('log', Value(log))
    if message is not None:
        updates['message'] = message
    
    if updates:
        # Perform the update directly in the database
        self.__class__.objects.filter(pk=self.pk).update(**updates)
        
        # Sync the message field in memory to keep the instance consistent
        if message is not None:
            self.message = message
        
        # We don't sync log to memory—next time we update it, we'll use Concat again
        # If you ever need the latest log value in memory, call refresh_from_db(fields=['log']) only when necessary

Why This Works #

• No more duplicate appends: Since we're not storing the Concat expression on the instance, subsequent calls to update (even just for message) won't re-run the log concatenation.
• Keeps performance high: We never read the existing log value from the database—all updates are done in a single write operation.
• Maintains consistency for other fields: We sync the message field in memory so your model instance doesn't have stale values for fields you updated.

If you ever need to access the latest log value in your code (e.g., to display it), you can call self.refresh_from_db(fields=['log']) at that point instead of after every update—this way you only pay the read cost when you actually need it.

内容的提问来源于stack exchange，提问作者AntiElephant