#33114: StringAgg always fails on TextField
-------------------------------------+-------------------------------------
     Reporter:  Swen Kooij           |                    Owner:  nobody
         Type:  Uncategorized        |                   Status:  new
    Component:  Database layer       |                  Version:  3.2
  (models, ORM)                      |
     Severity:  Normal               |               Resolution:
     Keywords:                       |             Triage Stage:
                                     |  Unreviewed
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------

Comment (by Swen Kooij):

 Sorry, I didn't quite grasp from that part of the release notes that this
 is expected.

 Setting a default `output_field` on `StringAgg` would help. It would
 restore the original behaviour. It's a bit strange to get this error when
 dealing with strings. Whether it's a `CharField` or `TextField`, you still
 end up with a string in Python. Having to explicitly add an `output_field`
 for `StringAgg` seems to be just an annoyance.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/33114#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.d22b3094e97a756f1adff57500f51ebf%40djangoproject.com.

Reply via email to