Re: [Django] #19580: Unify reverse foreign key and m2m unsaved model querying

2024-01-15 Thread Django 
#19580: Unify reverse foreign key and m2m unsaved model querying
-+-
 Reporter:  Anssi Kääriäinen |Owner:  raydeal
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Adam Sołtysik):

 I agree with the above. Why does something like this (where `self` is an
 unsaved `User` instance)

 {{{Book.objects.filter(author=self).exists()}}}

 display a proper `RemovedInDjango50Warning`, while equivalent

 {{{self.books.exists()}}}

 suddenly crashes? This is totally unexpected.

-- 
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/0107018d0df8e9de-77692f4d-2f34-4215-9acb-ff5ecea8b415-00%40eu-central-1.amazonses.com.

Re: [Django] #19580: Unify reverse foreign key and m2m unsaved model querying

2023-10-09 Thread Django 
#19580: Unify reverse foreign key and m2m unsaved model querying
-+-
 Reporter:  Anssi Kääriäinen |Owner:  raydeal
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Alex Matos):

 I work on a large Django codebase and while upgrading it from version 3.2
 to 4.2 a lot of code broke due to this change, where code that was once
 returning an empty queryset, now raises a `ValueError`. In my opinion,
 this change should be fully reverted. The partial update from #33952 is
 not enough. I'm pretty sure I'm not alone in this situation. One of
 Django's core strengths has always been its stability and breaking user
 code without even a deprecation warning should be avoided at all costs.

-- 
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/0107018b14e3b3d5-ce829a34-058e-4598-ae11-9968622f88f8-00%40eu-central-1.amazonses.com.

Re: [Django] #19580: Unify reverse foreign key and m2m unsaved model querying

2022-02-23 Thread Django 
#19580: Unify reverse foreign key and m2m unsaved model querying
-+-
 Reporter:  Anssi Kääriäinen |Owner:  raydeal
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Mariusz Felisiak):

 > Should we consider making this a deprecation warning for now, and adding
 the strict validation in Django 5.x instead? (Admittedly, this isn't the
 sort of thing you can write a startup check for, so it may be that a
 deprecation warning would only help for apps that have good test coverage
 anyhow.)

 IMO deprecation is unnecessary, we raise an exception so it's not
 something can be easily missed. Also, this is undocumented behavior and as
 far as I'm aware it should be quite rare. If you think deprecation is
 necessary, please first start a discussion on the DevelopersMailingList,
 where you'll reach a wider audience and see what other think.

-- 
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/066.a0bb5bf40534a981e6838e26236107fe%40djangoproject.com.

Re: [Django] #19580: Unify reverse foreign key and m2m unsaved model querying

2022-02-23 Thread Django 
#19580: Unify reverse foreign key and m2m unsaved model querying
-+-
 Reporter:  Anssi Kääriäinen |Owner:  raydeal
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Matt Westcott):

 * cc: Matt Westcott (added)


Comment:

 Ran across this while bringing Wagtail up to date with Django main. I
 appreciate that accessing a reverse-FK relation on an unsaved instance is
 undefined behaviour, so this isn't technically a breaking change -
 however, I suspect there could be a lot of code in the wild that's doing
 this unwittingly, in which case this change might be more disruptive than
 expected.

 For example, I had to make this fix:
 
https://github.com/wagtail/wagtail/pull/8028/commits/9e19bf63dbb698a4f57b131b6f8ae92bab7c2606
 - where I'd implemented something approximating an InlineFormSet, but
 neglected to make a special case for the 'create' view, and so it ends up
 querying an unsaved instance to arrive at the initial empty formset. I
 imagine this will be a fairly common gotcha in user code.

 (for the record, Wagtail also does much more esoteric things with faking
 relations on in-memory objects to support previews and saving drafts, but
 I'm willing to take the hit for that :-) )

 Should we consider making this a deprecation warning for now, and adding
 the strict validation in Django 5.x instead? (Admittedly, this isn't the
 sort of thing you can write a startup check for, so it may be that a
 deprecation warning would only help for apps that have good test coverage
 anyhow.)

-- 
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/066.d6563b503f09a89bbc04b9ee7266d835%40djangoproject.com.

Re: [Django] #19580: Unify reverse foreign key and m2m unsaved model querying

2022-02-22 Thread Django 
#19580: Unify reverse foreign key and m2m unsaved model querying
-+-
 Reporter:  Anssi Kääriäinen |Owner:  raydeal
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Mariusz Felisiak ):

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


Comment:

 In [changeset:"7ba6ebe9149ae38257d70100e8bfbfd0da189862" 7ba6ebe9]:
 {{{
 #!CommitTicketReference repository=""
 revision="7ba6ebe9149ae38257d70100e8bfbfd0da189862"
 Fixed #19580 -- Unified behavior of reverse foreign key and many-to-many
 relations for unsaved instances.
 }}}

-- 
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/066.732ac24886a63bd3fc910cc84ca1a26c%40djangoproject.com.

Re: [Django] #19580: Unify reverse foreign key and m2m unsaved model querying

2022-02-22 Thread Django 
#19580: Unify reverse foreign key and m2m unsaved model querying
-+-
 Reporter:  Anssi Kääriäinen |Owner:  raydeal
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * stage:  Accepted => Ready for checkin


-- 
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/066.5a6fa443799def2d983d19a2fe5a6a73%40djangoproject.com.

Re: [Django] #19580: Unify reverse foreign key and m2m unsaved model querying

2022-02-21 Thread Django 
#19580: Unify reverse foreign key and m2m unsaved model querying
-+-
 Reporter:  Anssi Kääriäinen |Owner:  raydeal
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by raydeal):

 * needs_better_patch:  1 => 0


-- 
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/066.9153c7ad04c219eeb901160ba7cc1462%40djangoproject.com.

Re: [Django] #19580: Unify reverse foreign key and m2m unsaved model querying

2022-02-08 Thread Django 
#19580: Unify reverse foreign key and m2m unsaved model querying
-+-
 Reporter:  Anssi Kääriäinen |Owner:  raydeal
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * needs_better_patch:  0 => 1


-- 
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/066.dbc00c15564b7856b1b60878198ba3a5%40djangoproject.com.

Re: [Django] #19580: Unify reverse foreign key and m2m unsaved model querying

2022-01-27 Thread Django 
#19580: Unify reverse foreign key and m2m unsaved model querying
-+-
 Reporter:  Anssi Kääriäinen |Owner:  raydeal
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by raydeal):

 * needs_better_patch:  1 => 0


-- 
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/066.90c695245f902aac94ef6d23b6aea971%40djangoproject.com.

Re: [Django] #19580: Unify reverse foreign key and m2m unsaved model querying

2022-01-25 Thread Django 
#19580: Unify reverse foreign key and m2m unsaved model querying
-+-
 Reporter:  Anssi Kääriäinen |Owner:  raydeal
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-

Comment (by raydeal):

 Replying to [comment:49 Mariusz Felisiak]:
 Right, now I better understand what is expected solution. I am going to
 review again previous patch and change this one.

-- 
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/066.946b781bd4e211d6a9af0275755faea2%40djangoproject.com.

Re: [Django] #19580: Unify reverse foreign key and m2m unsaved model querying

2022-01-25 Thread Django 
#19580: Unify reverse foreign key and m2m unsaved model querying
-+-
 Reporter:  Anssi Kääriäinen |Owner:  raydeal
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * needs_better_patch:  0 => 1


Comment:

 Replying to [comment:47 raydeal]:
 > I couldn't find correct rules because M2M worked as always, only changed
 behaviour of FK. When object is not saved it raises ValueError, when saved
 but related value is None returns , which is not consistent
 for me. Why?
 > Base on doubt from #17541
 https://code.djangoproject.com/ticket/17541#comment:8 I asked myself: What
 is the difference between not saved object with id (pk) refrerenced from
 other object and saved object with field containing None value referenced
 by other object, through FK both, from the relation point of view?
 > There is no difference - both of them have None value and making related
 query in both cases doesn't make sens.

 There is a huge difference for me. It's doesn't matter which field is
 pointed by m2m field, that's not crucial. The most important thing is that
 `Foo()` doesn't exist in the database so any related query makes no sense,
 and IMO we should raise an exception only in this particular case. You can
 start a discussion on DevelopersMailingList if you don't agree, where
 you'll reach a wider audience and see what other think.

 Moreover proposed change is not a part of the ticket description, it's
 backward incompatible, and was not accepted per se.

-- 
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/066.b310ca2fbc7a49496ad0082dc2f02449%40djangoproject.com.

Re: [Django] #19580: Unify reverse foreign key and m2m unsaved model querying

2022-01-24 Thread Django 
#19580: Unify reverse foreign key and m2m unsaved model querying
-+-
 Reporter:  Anssi Kääriäinen |Owner:  raydeal
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by raydeal):

 * needs_better_patch:  1 => 0
 * needs_tests:  1 => 0


-- 
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/066.68c1242d7b5c44f9314a6347c6b4936d%40djangoproject.com.

Re: [Django] #19580: Unify reverse foreign key and m2m unsaved model querying

2022-01-23 Thread Django 
#19580: Unify reverse foreign key and m2m unsaved model querying
-+-
 Reporter:  Anssi Kääriäinen |Owner:  raydeal
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-

Comment (by raydeal):

 My patch is implemented using different approach then previous. It changes
 behaviour of FK to be the same as M2M.

 I went through discussion in this and #17541 ticket and PR for them and
 analysed examples.
 This information in the ticket
 " There is a (slightly stale) patch for #17541 which makes fk fields and
 m2m fields work consistently."
 may be true 9 years ago, but now it is not consistent with M2M.

 I have also tested previous patch
 (https://github.com/django/django/pull/13784) locally.
 I couldn't find correct rules because M2M worked as always, only changed
 behaviour of FK. When object is not saved it raises ValueError, when saved
 but related value is Null returns , which is not consistent
 for me. Why?
 Base on doubt from #17541
 https://code.djangoproject.com/ticket/17541#comment:8 I asked myself: What
 is the difference between not saved object with id (pk) refrerenced from
 other object and saved object with field containing Null value referenced
 by other object, through FK both, from the relation point of view?
 There is no difference - both of them have Null value and making related
 query in both cases doesn't make sens.

 So finally I came to the conclusion that what M2M is doing is correct - in
 both cases it raises error - and it meet some of The Zen of Python rules,
 I think :)

-- 
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/066.61fb75159e5a5926c248ed4ebc84bb48%40djangoproject.com.

Re: [Django] #19580: Unify reverse foreign key and m2m unsaved model querying

2022-01-20 Thread Django 
#19580: Unify reverse foreign key and m2m unsaved model querying
-+-
 Reporter:  Anssi Kääriäinen |Owner:  raydeal
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * needs_better_patch:  0 => 1
 * needs_tests:  0 => 1


-- 
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/066.8230e7a6098aaafe6d18be968ab44022%40djangoproject.com.

Re: [Django] #19580: Unify reverse foreign key and m2m unsaved model querying

2022-01-14 Thread Django 
#19580: Unify reverse foreign key and m2m unsaved model querying
-+-
 Reporter:  Anssi Kääriäinen |Owner:  raydeal
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by raydeal):

 * needs_better_patch:  1 => 0


-- 
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/066.05d7a00d95a1af1f5ab7c69f4fbba012%40djangoproject.com.

Re: [Django] #19580: Unify reverse foreign key and m2m unsaved model querying

2022-01-12 Thread Django 
#19580: Unify reverse foreign key and m2m unsaved model querying
-+-
 Reporter:  Anssi Kääriäinen |Owner:  raydeal
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-

Comment (by raydeal):

 Replying to [comment:43 Ayush Joshi]:
 > raydeal if you are currently unable to work on this ticket then you can
 assign it to me.
 I am working on the ticket

-- 
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/066.8f8e46268e8d5fbfe1c9f3e92843a709%40djangoproject.com.

Re: [Django] #19580: Unify reverse foreign key and m2m unsaved model querying

2022-01-11 Thread Django 
#19580: Unify reverse foreign key and m2m unsaved model querying
-+-
 Reporter:  Anssi Kääriäinen |Owner:  raydeal
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Ayush Joshi):

 raydeal if you are currently unable to work on this ticket then you can
 assign it to me.

-- 
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/066.8a75e61d299ad9d0c0d3d8f6807171cc%40djangoproject.com.

Re: [Django] #19580: Unify reverse foreign key and m2m unsaved model querying

2022-01-03 Thread Django 
#19580: Unify reverse foreign key and m2m unsaved model querying
-+-
 Reporter:  Anssi Kääriäinen |Owner:  raydeal
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Pavel Druzhinin):

 Replying to [comment:41 Asif Saifuddin Auvi]:
 > Replying to [comment:40 raydeal]:
 > > Replying to [comment:38 Pavel Druzhinin]:
 > > > Replying to [comment:37 Mariusz Felisiak]:
 > > > > Thanks for this patch, however it's not ready for review. Please
 fix tests and `isort`.
 > > >
 > > > Hello, it seems I need help to fix this error. I'm not sure code
 from previous contributor is correct and I don't fully understand the
 subject of this bug (m2m relations).
 > > > What is better to do: remove label `easy pickings` and try another
 bug or someone could help me with fixing this bug?
 > > >
 > > > P.S. Please, don't think for nagging. I really don't want to drop
 the ticket silently and want to continue to contribute at the same time.
 Thanks in advance with your advice how best to proceed.
 > >
 > > Would you like to carry on with the ticket? I can help you. After
 reading comments and code my understanding is to make FK reverse working
 the same way as m2m when id=None, what is done in code, but message is a
 bit different, it would be good to have similar message in both cases. It
 will require amend m2m tests as well after update with current django
 version.
 >
 >
 > you should take over the ticket and create a new PR as it seems he is
 not able to fix the issue

 I agree with this proposal, you could change an assignee. 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/066.415a682ee6997353de323b1d07001c8f%40djangoproject.com.

Re: [Django] #19580: Unify reverse foreign key and m2m unsaved model querying

2021-12-31 Thread Django 
#19580: Unify reverse foreign key and m2m unsaved model querying
-+-
 Reporter:  Anssi Kääriäinen |Owner:  raydeal
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Asif Saifuddin Auvi):

 Replying to [comment:40 raydeal]:
 > Replying to [comment:38 Pavel Druzhinin]:
 > > Replying to [comment:37 Mariusz Felisiak]:
 > > > Thanks for this patch, however it's not ready for review. Please fix
 tests and `isort`.
 > >
 > > Hello, it seems I need help to fix this error. I'm not sure code from
 previous contributor is correct and I don't fully understand the subject
 of this bug (m2m relations).
 > > What is better to do: remove label `easy pickings` and try another bug
 or someone could help me with fixing this bug?
 > >
 > > P.S. Please, don't think for nagging. I really don't want to drop the
 ticket silently and want to continue to contribute at the same time.
 Thanks in advance with your advice how best to proceed.
 >
 > Would you like to carry on with the ticket? I can help you. After
 reading comments and code my understanding is to make FK reverse working
 the same way as m2m when id=None, what is done in code, but message is a
 bit different, it would be good to have similar message in both cases. It
 will require amend m2m tests as well after update with current django
 version.


 you should take over the ticket and create a new PR as it seems he is not
 able to fix the issue

-- 
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/066.99d96a9ded6e6e2747329bbbf8b9fd20%40djangoproject.com.

Re: [Django] #19580: Unify reverse foreign key and m2m unsaved model querying

2021-12-27 Thread Django 
#19580: Unify reverse foreign key and m2m unsaved model querying
-+-
 Reporter:  Anssi Kääriäinen |Owner:  raydeal
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-

Comment (by raydeal):

 Replying to [comment:38 Pavel Druzhinin]:
 > Replying to [comment:37 Mariusz Felisiak]:
 > > Thanks for this patch, however it's not ready for review. Please fix
 tests and `isort`.
 >
 > Hello, it seems I need help to fix this error. I'm not sure code from
 previous contributor is correct and I don't fully understand the subject
 of this bug (m2m relations).
 > What is better to do: remove label `easy pickings` and try another bug
 or someone could help me with fixing this bug?
 >
 > P.S. Please, don't think for nagging. I really don't want to drop the
 ticket silently and want to continue to contribute at the same time.
 Thanks in advance with your advice how best to proceed.

 Would you like to carry on with the ticket? After reading comments and
 code my understanding is to make FK reverse working the same way as m2m
 when id=None, what is done in code, but message is a bit different, it
 would be good to have similar message in both cases. It will require amend
 m2m tests as well after update with current django version.

-- 
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/066.15198a282c9147004bd23efc674b329c%40djangoproject.com.

Re: [Django] #19580: Unify reverse foreign key and m2m unsaved model querying

2021-12-22 Thread Django 
#19580: Unify reverse foreign key and m2m unsaved model querying
-+-
 Reporter:  Anssi Kääriäinen |Owner:  raydeal
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by raydeal):

 * owner:  (none) => raydeal


Comment:

 I would like to look at code and try to improve the patch.

-- 
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/066.c446bea8a1acd7a843a0fb35e4f190f9%40djangoproject.com.

Re: [Django] #19580: Unify reverse foreign key and m2m unsaved model querying

2021-02-24 Thread Django 
#19580: Unify reverse foreign key and m2m unsaved model querying
-+-
 Reporter:  Anssi Kääriäinen |Owner:  Pavel
 Type:   |  Druzhinin
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Pavel Druzhinin):

 * owner:  (none) => Pavel Druzhinin
 * status:  new => assigned


-- 
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/066.11120e61cbb23c3de79697a89a017e7d%40djangoproject.com.

Re: [Django] #19580: Unify reverse foreign key and m2m unsaved model querying

2021-02-24 Thread Django 
#19580: Unify reverse foreign key and m2m unsaved model querying
-+-
 Reporter:  Anssi Kääriäinen |Owner:  (none)
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Pavel Druzhinin):

 * owner:  Pavel Druzhinin => (none)
 * status:  assigned => new


-- 
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/066.7d37bf696246ee64f719179f9ac302fb%40djangoproject.com.

Re: [Django] #19580: Unify reverse foreign key and m2m unsaved model querying

2021-02-23 Thread Django 
#19580: Unify reverse foreign key and m2m unsaved model querying
-+-
 Reporter:  Anssi Kääriäinen |Owner:  Pavel
 Type:   |  Druzhinin
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Pavel Druzhinin):

 Replying to [comment:37 Mariusz Felisiak]:
 > Thanks for this patch, however it's not ready for review. Please fix
 tests and `isort`.

 Hello, it seems I need help to fix this error. I'm not sure code from
 previous contributor is correct and I don't fully understand the subject
 of this bug (m2m relations).
 What is better to do: remove label `easy pickings` and try another bug or
 someone could help me with fixing this bug?

 P.S. Please, don't think for nagging. I really don't want to drop the
 ticket silently and want to continue to contribute at the same time.
 Thanks in advance with your advice how best to proceed.

-- 
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/066.ed3fd074c068e289d3f71f0a29c6d722%40djangoproject.com.

Re: [Django] #19580: Unify reverse foreign key and m2m unsaved model querying

2020-12-29 Thread Django 
#19580: Unify reverse foreign key and m2m unsaved model querying
-+-
 Reporter:  Anssi Kääriäinen |Owner:  Pavel
 Type:   |  Druzhinin
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * needs_better_patch:  0 => 1


Comment:

 Thanks for this patch, however it's not ready for review. Please fix tests
 and `isort`.

-- 
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/066.1ca024d1697ab8ff38f2cdc8baeeaf22%40djangoproject.com.

Re: [Django] #19580: Unify reverse foreign key and m2m unsaved model querying

2020-12-29 Thread Django 
#19580: Unify reverse foreign key and m2m unsaved model querying
-+-
 Reporter:  Anssi Kääriäinen |Owner:  Pavel
 Type:   |  Druzhinin
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Pavel Druzhinin):

 * needs_docs:  1 => 0
 * needs_tests:  1 => 0


Comment:

 PR has been updated https://github.com/django/django/pull/13784

-- 
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/066.4e0e955add3b012477c3a6ccddb7d930%40djangoproject.com.

Re: [Django] #19580: Unify reverse foreign key and m2m unsaved model querying

2020-12-29 Thread Django 
#19580: Unify reverse foreign key and m2m unsaved model querying
-+-
 Reporter:  Anssi Kääriäinen |Owner:  Pavel
 Type:   |  Druzhinin
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Pavel Druzhinin):

 Rebased the previous PR https://github.com/django/django/pull/11807.
 I would like to get some clarification on this old ticket, took it under
 easy-pickings tag.

 https://github.com/django/django/pull/11807#pullrequestreview-344544165 -
 this is the last comment from where I started to search next steps to
 complete the ticket.
 It leads to the undone comments:

 1. https://github.com/django/django/pull/8570#pullrequestreview-113177526
 Should I move all tests from m2m_through_regress to many_to_many or some
 particular tests?

 2. https://github.com/django/django/pull/8570#pullrequestreview-113506649
 I see prepared changelogs in comment
 https://github.com/django/django/pull/11807#issuecomment-612404721, but
 don't know where to place them in codebase. Could you explain?

 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/066.15e193518a566e13299f1f1552d8b1ce%40djangoproject.com.

Re: [Django] #19580: Unify reverse foreign key and m2m unsaved model querying

2020-12-17 Thread Django 
#19580: Unify reverse foreign key and m2m unsaved model querying
-+-
 Reporter:  Anssi Kääriäinen |Owner:  Pavel
 Type:   |  Druzhinin
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Pavel Druzhinin):

 Need some help with the ticket. PR:
 https://github.com/django/django/pull/13784.
 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/066.ecc0a9b5e574bbe50e735d7b044eec46%40djangoproject.com.

Re: [Django] #19580: Unify reverse foreign key and m2m unsaved model querying

2020-12-08 Thread Django 
#19580: Unify reverse foreign key and m2m unsaved model querying
-+-
 Reporter:  Anssi Kääriäinen |Owner:  Pavel
 Type:   |  Druzhinin
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Pavel Druzhinin):

 * owner:  (none) => Pavel Druzhinin
 * status:  new => assigned


Comment:

 I'd like to try finish this

-- 
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/066.7f413a4747c615f52fb7a819aae3403e%40djangoproject.com.

Re: [Django] #19580: Unify reverse foreign key and m2m unsaved model querying

2020-12-02 Thread Django 
#19580: Unify reverse foreign key and m2m unsaved model querying
-+-
 Reporter:  Anssi Kääriäinen |Owner:  (none)
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Manav Agarwal):

 * owner:  Manav Agarwal => (none)
 * status:  assigned => new


-- 
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/066.20a4c61ac2e21ace758baedebe49bc66%40djangoproject.com.

Re: [Django] #19580: Unify reverse foreign key and m2m unsaved model querying

2020-11-13 Thread Django 
#19580: Unify reverse foreign key and m2m unsaved model querying
-+-
 Reporter:  Anssi Kääriäinen |Owner:  Manav
 Type:   |  Agarwal
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Manav Agarwal):

 * owner:  Ahsan Shafiq => Manav Agarwal


-- 
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/066.54740081dbc566715abfb16aff4eb46c%40djangoproject.com.

Re: [Django] #19580: Unify reverse foreign key and m2m unsaved model querying

2020-10-21 Thread Django 
#19580: Unify reverse foreign key and m2m unsaved model querying
-+-
 Reporter:  Anssi Kääriäinen |Owner:  Ahsan
 Type:   |  Shafiq
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Manav Agarwal):

 Can I claim this? I think I can move this forward

-- 
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/066.c9a293e6cc561d729dce6b83c1814e4c%40djangoproject.com.

Re: [Django] #19580: Unify reverse foreign key and m2m unsaved model querying

2020-01-17 Thread Django 
#19580: Unify reverse foreign key and m2m unsaved model querying
-+-
 Reporter:  Anssi Kääriäinen |Owner:  Ahsan
 Type:   |  Shafiq
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by felixxm):

 * needs_docs:  0 => 1
 * needs_tests:  0 => 1


-- 
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/066.047659a75d336be2beaea4d58865e6dd%40djangoproject.com.

Re: [Django] #19580: Unify reverse foreign key and m2m unsaved model querying

2019-09-23 Thread Django 
#19580: Unify reverse foreign key and m2m unsaved model querying
-+-
 Reporter:  Anssi Kääriäinen |Owner:  Ahsan
 Type:   |  Shafiq
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Ahsan Shafiq):

 * needs_better_patch:  1 => 0


Comment:

 https://github.com/django/django/pull/11807

-- 
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/066.c377dded68f4bdb83a3e4402b22cde64%40djangoproject.com.

Re: [Django] #19580: Unify reverse foreign key and m2m unsaved model querying

2019-09-18 Thread Django 
#19580: Unify reverse foreign key and m2m unsaved model querying
-+-
 Reporter:  Anssi Kääriäinen |Owner:  Ahsan
 Type:   |  Shafiq
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Ahsan Shafiq):

 * owner:  (none) => Ahsan Shafiq
 * status:  new => assigned


-- 
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/066.31a2a1af6aa42491954488c8d7346bd5%40djangoproject.com.

Re: [Django] #19580: Unify reverse foreign key and m2m unsaved model querying

2019-09-18 Thread Django 
#19580: Unify reverse foreign key and m2m unsaved model querying
-+-
 Reporter:  Anssi Kääriäinen |Owner:  (none)
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by felixxm):

 * status:  assigned => new
 * owner:  Rajesh Veeranki => (none)


-- 
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/066.41e90d3ce481f3d788fc71ca433a3583%40djangoproject.com.

Re: [Django] #19580: Unify reverse foreign key and m2m unsaved model querying

2019-04-14 Thread Django 
#19580: Unify reverse foreign key and m2m unsaved model querying
-+-
 Reporter:  Anssi Kääriäinen |Owner:  Rajesh
 Type:   |  Veeranki
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Robert Švab):

 Hi everyone, I'm interested in contributing to Django, so would like to
 finish this easy pick if needed. From comments on PR I can see there is
 only few things left, adjustments to tests and docs. Advise me if there is
 anything else left.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.602e0ea4a6094096429fca4cf306a085%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #19580: Unify reverse foreign key and m2m unsaved model querying

2018-04-19 Thread Django 
#19580: Unify reverse foreign key and m2m unsaved model querying
-+-
 Reporter:  Anssi Kääriäinen |Owner:  Rajesh
 Type:   |  Veeranki
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Carlton Gibson):

 * needs_better_patch:  0 => 1


-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.291dd18dd65e18cc4e5ed3608f0dc4bc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #19580: Unify reverse foreign key and m2m unsaved model querying

2018-04-12 Thread Django 
#19580: Unify reverse foreign key and m2m unsaved model querying
-+-
 Reporter:  Anssi Kääriäinen |Owner:  Rajesh
 Type:   |  Veeranki
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Rajesh Veeranki):

 * needs_better_patch:  1 => 0


-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.bae4c777020b5d795c2ded55abcc02c1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #19580: Unify reverse foreign key and m2m unsaved model querying

2018-02-28 Thread Django 
#19580: Unify reverse foreign key and m2m unsaved model querying
-+-
 Reporter:  Anssi Kääriäinen |Owner:  Rajesh
 Type:   |  Veeranki
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Carlton Gibson):

 * needs_better_patch:  0 => 1


Comment:

 Comments on
 [https://github.com/django/django/pull/8570#pullrequestreview-10437
 PR]

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.1aafcdf045374351cfc88a32d1c09de6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #19580: Unify reverse foreign key and m2m unsaved model querying

2017-06-23 Thread Django 
#19580: Unify reverse foreign key and m2m unsaved model querying
-+-
 Reporter:  Anssi Kääriäinen |Owner:  Rajesh
 Type:   |  Veeranki
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Rajesh Veeranki):

 * needs_better_patch:  1 => 0


--
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.8e5456e3c62ef8cff8d40b239fb98d25%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #19580: Unify reverse foreign key and m2m unsaved model querying

2017-05-29 Thread Django 
#19580: Unify reverse foreign key and m2m unsaved model querying
-+-
 Reporter:  Anssi Kääriäinen |Owner:  Rajesh
 Type:   |  Veeranki
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Rajesh Veeranki):

 * owner:  (none) => Rajesh Veeranki
 * status:  new => assigned


Comment:

 Please review the latest PR, that is rebased with the master here:
 https://github.com/django/django/pull/8570
 The tests look okay to me. Please suggest any more tests if required.
 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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.5fe16e92318aeaf64655ca95182e9e8a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #19580: Unify reverse foreign key and m2m unsaved model querying

2017-05-11 Thread Django 
#19580: Unify reverse foreign key and m2m unsaved model querying
-+-
 Reporter:  Anssi Kääriäinen |Owner:  (none)
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Harikishen H):

 * owner:  Harikishen H => (none)
 * status:  assigned => new


--
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.3200874d8c79c14adc3a46f371e2dfd5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #19580: Unify reverse foreign key and m2m unsaved model querying

2017-05-11 Thread Django 
#19580: Unify reverse foreign key and m2m unsaved model querying
-+-
 Reporter:  Anssi Kääriäinen |Owner:
 Type:   |  harikishen
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by harikishen):

 * owner:  (none) => harikishen
 * status:  new => assigned


Comment:

 I have used the django framework for some of my projects. I would love to
 give back. I would like to work on this bug.

--
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.5289f8d0600f7ef29fa7d787990fcc66%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #19580: Unify reverse foreign key and m2m unsaved model querying

2017-05-06 Thread Django 
#19580: Unify reverse foreign key and m2m unsaved model querying
-+-
 Reporter:  Anssi Kääriäinen |Owner:  (none)
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Tim Graham):

 That's a correct assessment of the situation.

--
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.396c80672b703a367487dcb2b2c34508%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #19580: Unify reverse foreign key and m2m unsaved model querying

2017-05-06 Thread Django 
#19580: Unify reverse foreign key and m2m unsaved model querying
-+-
 Reporter:  Anssi Kääriäinen |Owner:  (none)
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Lander Kerbey):

 Newbie here, but I've begun reading through this problem and would like to
 take a crack at it. Andrey's pull request seems most of the way there, and
 if the comments remain valid that gives me a starting point. Thoughts?

--
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.a0012d9f55e29b1540a2036d3c8b1aa2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #19580: Unify reverse foreign key and m2m unsaved model querying

2017-05-06 Thread Django 
#19580: Unify reverse foreign key and m2m unsaved model querying
-+-
 Reporter:  Anssi Kääriäinen |Owner:  (none)
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Tim Graham):

 * status:  assigned => new
 * owner:  Andrey Kuzminov => (none)


Comment:

 I think someone else could pick this up considering we haven't heard from
 Andrey in a while.

--
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.44e2d3e42ac266e4c43d28c937ca7475%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #19580: Unify reverse foreign key and m2m unsaved model querying

2017-02-22 Thread Django 
#19580: Unify reverse foreign key and m2m unsaved model querying
-+-
 Reporter:  Anssi Kääriäinen |Owner:  Andrey
 Type:   |  Kuzminov
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-

Comment (by John McCann):

 Hi there, I was also wondering if further work is needed? From Tim's final
 comment in the pull request, it seems that most of the changes from Ansi's
 patch still haven't been updated in master. 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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.50077bcb38f4e36e5397a4d38ad384fc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #19580: Unify reverse foreign key and m2m unsaved model querying

2017-02-04 Thread Django 
#19580: Unify reverse foreign key and m2m unsaved model querying
-+-
 Reporter:  Anssi Kääriäinen |Owner:  Andrey
 Type:   |  Kuzminov
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-

Comment (by eadhina):

 Hey guys, is this ticket still need a fix ?

--
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.9607061930d602b10ab80c2b05b73180%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #19580: Unify reverse foreign key and m2m unsaved model querying

2016-12-23 Thread Django 
#19580: Unify reverse foreign key and m2m unsaved model querying
-+-
 Reporter:  Anssi Kääriäinen |Owner:  Andrey
 Type:   |  Kuzminov
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Tim Graham):

 * needs_better_patch:  0 => 1


--
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.1d77727f44ce454ebab305ec8f73dbcc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #19580: Unify reverse foreign key and m2m unsaved model querying

2016-12-11 Thread Django 
#19580: Unify reverse foreign key and m2m unsaved model querying
-+-
 Reporter:  Anssi Kääriäinen |Owner:  Andrey
 Type:   |  Kuzminov
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Ian Foote):

 * needs_better_patch:  0 => 1


--
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.284752718ec69befed4e8665f48d0bcb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #19580: Unify reverse foreign key and m2m unsaved model querying

2016-11-22 Thread Django 
#19580: Unify reverse foreign key and m2m unsaved model querying
-+-
 Reporter:  Anssi Kääriäinen |Owner:  Andrey
 Type:   |  Kuzminov
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Tim Graham):

 * needs_better_patch:  1 => 0


--
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.d1f878808095f81482c61685cbfc2da7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #19580: Unify reverse foreign key and m2m unsaved model querying

2016-11-05 Thread Django 
#19580: Unify reverse foreign key and m2m unsaved model querying
-+-
 Reporter:  Anssi Kääriäinen |Owner:  Andrey
 Type:   |  Kuzminov
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Olivier Tabone):

 added comments in the PR

--
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.dbb40f763dbcc6e769e0b22277d17ffa%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #19580: Unify reverse foreign key and m2m unsaved model querying

2016-11-05 Thread Django 
#19580: Unify reverse foreign key and m2m unsaved model querying
-+-
 Reporter:  Anssi Kääriäinen |Owner:  Andrey
 Type:   |  Kuzminov
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Olivier Tabone):

 * cc: olivier.tabone@… (added)


--
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.9d0f6046565aa5d4606c810303913b9d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #19580: Unify reverse foreign key and m2m unsaved model querying

2016-08-24 Thread Django 
#19580: Unify reverse foreign key and m2m unsaved model querying
-+-
 Reporter:  akaariai |Owner:  akuzminov
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-

Comment (by akuzminov):

 Thanks Tim, I'll add more tests next week

--
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.cdc1f4b4a738d17f70033dbf1dc2c60b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #19580: Unify reverse foreign key and m2m unsaved model querying

2016-08-16 Thread Django 
#19580: Unify reverse foreign key and m2m unsaved model querying
-+-
 Reporter:  akaariai |Owner:  akuzminov
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-

Comment (by timgraham):

 I left comments for improvement on the rebased
 [https://github.com/django/django/pull/7098 PR].

--
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.0e0a0f6f37ebbf9062dacb73228949ec%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #19580: Unify reverse foreign key and m2m unsaved model querying

2016-08-15 Thread Django 
#19580: Unify reverse foreign key and m2m unsaved model querying
-+-
 Reporter:  akaariai |Owner:  akuzminov
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by akuzminov):

 * owner:   => akuzminov
 * status:  new => assigned


--
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.29d2da6b6f0e7031567a534a0faf1b92%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #19580: Unify reverse foreign key and m2m unsaved model querying

2016-08-14 Thread Django 
#19580: Unify reverse foreign key and m2m unsaved model querying
-+-
 Reporter:  akaariai |Owner:
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-

Comment (by mscott250):

 Hi,

 I'm interested in contributing to Django and have been advised to start
 with some of the 'easy pickings' tasks. I've seen it's been unassigned and
 is still open, is this something I can pick up?

 Cheers,
 Michael

--
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.7df7b98a84561c5959ea5a98e599a9ef%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #19580: Unify reverse foreign key and m2m unsaved model querying

2016-08-12 Thread Django 
#19580: Unify reverse foreign key and m2m unsaved model querying
-+-
 Reporter:  akaariai |Owner:
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by timgraham):

 * owner:  ketanbhatt =>
 * status:  assigned => new


--
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.217b881c57ac1c5705457961c5914c96%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #19580: Unify reverse foreign key and m2m unsaved model querying

2016-07-25 Thread Django 
#19580: Unify reverse foreign key and m2m unsaved model querying
-+-
 Reporter:  akaariai |Owner:
 Type:   |  ketanbhatt
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-

Comment (by timgraham):

 Yes, you should
 [https://docs.djangoproject.com/en/dev/internals/contributing/writing-code
 /working-with-git/#rebasing-branches rebase the branch] and update the
 release notes for 1.11.

--
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.bea15cbb6143e2cc89bf7c68ed05bc9a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #19580: Unify reverse foreign key and m2m unsaved model querying

2016-05-30 Thread Django 
#19580: Unify reverse foreign key and m2m unsaved model querying
-+-
 Reporter:  akaariai |Owner:
 Type:   |  ketanbhatt
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by ketanbhatt):

 * status:  new => assigned
 * owner:  nobody => ketanbhatt


Comment:

 I will create a new branch, and make the changes made in
 https://github.com/django/django/compare/master...akaariai:ticket_17541

--
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.38638a5c676cf6f0881074b16f060bf3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #19580: Unify reverse foreign key and m2m unsaved model querying (was: Unify reverse foreign key and m2m querying behavior)

2016-05-30 Thread Django 
#19580: Unify reverse foreign key and m2m unsaved model querying
-+-
 Reporter:  akaariai |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by timgraham):

 * easy:  0 => 1


Comment:

 I think this would allow removing the two lines added in
 a4c20ae85b40c49e28d1b2227208e4f00d7820df.

 Marking as "Easy pickings" since rebasing Anssi's original patch might not
 be too difficult.

--
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.c93c4c6c8527c6a46842efcf440a57fe%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.