Changes between Version 2 and Version 3 of Ticket #34955, comment 7


Ignore:
Timestamp:
Nov 8, 2023, 9:16:17 AM (13 months ago)
Author:
David Sanders

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #34955, comment 7

    v2 v3  
    77 - Unfortunately we can't change `Concat()` to use `||` because on pg it _does_ evaluate NULLs. If it were to use `||` then we _would_ need to make use of `Coalesce()` to make it consistent.
    88 
    9 I'm kinda hoping though that we do get a (separate) immutable concat for pg because concatenating strings seems to be a common desire, at least for me :D
     9I'm kinda hoping though that we do get a (separate) immutable concat for pg because concatenating strings seems to be a common desire, at least for me :D  But at the same time I recognise how easy it is to create one and agree with the whole Django-isnt-a-kitchen-sink-framework.
    1010
    1111Lastly can I just say that (somewhat jokingly but semi-serious)... we may be missing the perfect opportunity to make use of the `__floordiv__()` operator method [3] ;D
Back to Top