Re: [Django] #7623: Multi-table inheritance: Add the ability create child instance from existing parent

[Django]

#7623: Multi-table inheritance: Add the ability create child instance from
existing parent
-+-
 Reporter:  brooks.travis@…  |Owner:  (none)
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  model-inheritance,   | Triage Stage:  Accepted
  multi-table-inheritance|
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by mrodal):

 * cc: mrodal (added)


Comment:

 wow, 11 years.. and it seems so simple to be able to insert a row with 1
 FK and the child fields..

-- 
Ticket URL: 
Django 
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/081.3d7bb9b08efbd82678e52fbad1f5683d%40djangoproject.com.

Re: [Django] #31097: StringAgg And ArrayAgg with filtering in subquery generates invalid string_agg() SQL function call

[Django]

#31097: StringAgg And ArrayAgg with filtering in subquery generates invalid
string_agg() SQL function call
-+-
 Reporter:  Laurent Tramoy   |Owner:  David
 |  Wobrock
 Type:  Bug  |   Status:  assigned
Component:  contrib.postgres |  Version:  3.0
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by David Wobrock):

 * has_patch:  0 => 1


Comment:

 The PR https://github.com/django/django/pull/12259

-- 
Ticket URL: 
Django 
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/064.773d7ea1b332faf1eb1af75bfef64b7e%40djangoproject.com.

Re: [Django] #31097: StringAgg And ArrayAgg with filtering in subquery generates invalid string_agg() SQL function call

[Django]

#31097: StringAgg And ArrayAgg with filtering in subquery generates invalid
string_agg() SQL function call
-+-
 Reporter:  Laurent Tramoy   |Owner:  David
 |  Wobrock
 Type:  Bug  |   Status:  assigned
Component:  contrib.postgres |  Version:  3.0
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by David Wobrock):

 Yes, I do reproduce on the latest {{{master}}}. I'll keep digging in that
 direction.

-- 
Ticket URL: 
Django 
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/064.1ac5f6bf2e17845cf8effc785f4f5562%40djangoproject.com.

Re: [Django] #31097: StringAgg And ArrayAgg with filtering in subquery generates invalid string_agg() SQL function call

[Django]

#31097: StringAgg And ArrayAgg with filtering in subquery generates invalid
string_agg() SQL function call
-+-
 Reporter:  Laurent Tramoy   |Owner:  David
 |  Wobrock
 Type:  Bug  |   Status:  assigned
Component:  contrib.postgres |  Version:  3.0
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Simon Charette):

 * cc: Simon Charette (added)


Comment:

 Did you manage to reproduce against the latest `master` as well? It looks
 like it might have been fixed by commits related to #31094.

 If it's still the case you seem to be heading in the right direction;
 there's likely an issue with `OrderableAggMixin` and the use of `filter`
 given how both require some special source expressions handling.

-- 
Ticket URL: 
Django 
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/064.6475e0d1406e2c3c354828c1a4533901%40djangoproject.com.

Re: [Django] #31097: StringAgg And ArrayAgg with filtering in subquery generates invalid string_agg() SQL function call

[Django]

#31097: StringAgg And ArrayAgg with filtering in subquery generates invalid
string_agg() SQL function call
-+-
 Reporter:  Laurent Tramoy   |Owner:  David
 |  Wobrock
 Type:  Bug  |   Status:  assigned
Component:  contrib.postgres |  Version:  3.0
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by David Wobrock):

 * status:  new => assigned
 * owner:  (none) => David Wobrock


Comment:

 Hi, I'm claiming the ticket if nobody bothers.
 I already wrote a testcase that reproduced the bug and started to pin down
 the source of the issue.

 The first (very) technical info I found:
 It seems to be linked to the logic of relabeling aliases of the the filter
 clause in {{{django.db.models.sql.query.Query.change_aliases}}}, in the
 {{{self.where.relabel_aliases(change_map)}}} logic.
 The first node itself is a {{{WhereNode}}} containing {{{(AND: (NOT (AND:
 )))}}}
 When going down the filter tree, we first hit again a {{{WhereNode}}} with
 the negation: {{{(NOT (AND: ))}}} for our exclude clause.
 Finally coming to the {{{Exact}}} object, we relabel the left hand-side of
 the condition, being the {{{StringAgg}}}.
 This calls the
 {{{django.db.models.expressions.BaseExpression.relabeled_clone}}} where we
 depend on the fields found by {{{self.get_source_expressions()}}}

 Either, those source expressions are incomplete because of the way the
 {{{OrderableAggMixin}}} plays with the {{{self.get_source_expressions()}}}
 (not calling the super), or the {{{change_map}}} which is passed down is
 missing some potential aliases.

 I'll try to keep investigating and propose a patch in the coming weeks :)

-- 
Ticket URL: 
Django 
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/064.b3aabc4a0f4529a531134e1c866b859f%40djangoproject.com.

Re: [Django] #31124: Model.get_FOO_display() does not work correctly with inherited choices.

[Django]

#31124: Model.get_FOO_display() does not work correctly with inherited choices.
-+-
 Reporter:  Yash Jhunjhunwala|Owner:  George
 |  Popides
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  3.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by George Popides):

 After digging in, i have found that the choices of B model are the same
 with the A model, despiite them being the proper ones in __init__.
 Migration is correct, so now i must find why the choices of model B are
 ignored.
 Being my first issue, some hints would be appreciated.
 Thanks

-- 
Ticket URL: 
Django 
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/061.70e68300990b184a6ffeb819e24f6e8e%40djangoproject.com.

Re: [Django] #28290: Doc sections are missing target (labels) links

[Django]

#28290: Doc sections are missing target (labels) links
-+-
 Reporter:  Tony Narlock |Owner:  Abhijeet
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:  docs labels  | Triage Stage:  Accepted
  intersphinx|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Abhijeet):

 * owner:  Kees Hink => Abhijeet
 * has_patch:  0 => 1


Comment:

 My patch: https://github.com/django/django/pull/12251
 Discussion: https://groups.google.com/forum/#!topic/django-developers
 /sRfq48rD-Ao

-- 
Ticket URL: 
Django 
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/062.0514e2e05adbbc0dfee7930cbeefabc4%40djangoproject.com.