Changes between Version 2 and Version 3 of Ticket #34940, comment 3


Ignore:
Timestamp:
Nov 3, 2023, 1:37:28 AM (13 months ago)
Author:
David Sanders

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #34940, comment 3

    v2 v3  
    1 There is a way to achieve this, but I've only tested this with PostgreSQL and it **only** works with psycopg2 – psycopg (3) changes the way composite type adaptation works.  (what's more confusing is that if you try this with psycopg (3) it _mogrifies_ fine but if you try to run the query it fails.)
     1There is a way to achieve this, but I've only tested this with PostgreSQL and it **only** works with psycopg2 – psycopg (3) changes the way composite type adaptation works[1].  (what's more confusing is that if you try this with psycopg (3) it _mogrifies_ fine but if you try to run the query it fails.)
    22
    33{{{
     
    2525
    2626Disclaimer: This is not an official Django recommendation, merely my own personal testing out of curiosity :D
     27
     28[1]: https://www.psycopg.org/psycopg3/docs/basic/from_pg2.html#you-cannot-use-in-s-with-a-tuple
Back to Top