#35344: GeneratedField get_col output_field bug
-------------------------------------+-------------------------------------
     Reporter:  Johannes Westphal    |                    Owner:  Johannes
                                     |  Westphal
         Type:  Bug                  |                   Status:  closed
    Component:  Database layer       |                  Version:  dev
  (models, ORM)                      |
     Severity:  Release blocker      |               Resolution:  fixed
     Keywords:                       |             Triage Stage:  Ready for
                                     |  checkin
    Has patch:  1                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Changes (by Johannes Westphal <jojo@…>):

 * resolution:   => fixed
 * status:  assigned => closed

Comment:

 In [changeset:"5f180216409d75290478c71ddb0ff8a68c91dc16" 5f18021]:
 {{{#!CommitTicketReference repository=""
 revision="5f180216409d75290478c71ddb0ff8a68c91dc16"
 Fixed #35344, Refs #34838 -- Corrected output_field of resolved columns
 for GeneratedFields in aliased tables.

 Thanks Simon Charette for the review.
 }}}
-- 
Ticket URL: <https://code.djangoproject.com/ticket/35344#comment:10>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018e9c5f0cd7-42bcff1b-d573-4742-875d-e294913a5125-000000%40eu-central-1.amazonses.com.

Reply via email to