Changes between Version 2 and Version 3 of Ticket #36748


Ignore:
Timestamp:
Nov 20, 2025, 9:36:33 AM (3 hours ago)
Author:
Simon Charette
Comment:

Thanks for the excellent report and patch Chris!

The only part missing is a release note for 5.2.9 as this is a bug in a newly introduced feature and thus still qualifies for backport.

I don't know if this will always be the case, so I suggest keeping the present filter too.

I also think it's worth keeping both as well as they are cheap to perform and could cover other cases in the wild.

Small note to me that this relates to #36727 but the latter won't fix issue as, just like you said, get_placeholder can be a function of value. This only means we'll need even more logic to handle the presence of either get_placeholder or get_placeholder_sql.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #36748

    • Property Severity NormalRelease blocker
    • Property Triage Stage UnreviewedAccepted
  • Ticket #36748 – Description

    v2 v3  
    3636
    3737I bumped into this regression when upgrading to 5.2 and the call to a Postgres extension function in such a placeholder, but which has a db_type that is present in self.connection.data_types, didn't happen anymore for bulk inserts.
    38 
    39 
    40 **NB This bug can go unnoticed: bulk_create might succeed, but with different data written to disk than what is expected. And subsequent reads and seeks will have the wrong results.**
Back to Top