date:20170113

Re: [Django] #27718: Add QuerySet.union(), intersection(), difference() (was: Add QuerySet.union(), intersect(), minus())

2017-01-13 Thread Django

#27718: Add QuerySet.union(), intersection(), difference()
-+-
 Reporter:  Florian Apolloner|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (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:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * needs_docs:  1 => 0
 * 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 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.477506ee62312e1669552036aab3e22f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #5851: SplitDateTimeWidget (or MultiWidget) doesn't allow different attrs for different fields

2017-01-13 Thread Django

#5851: SplitDateTimeWidget (or MultiWidget) doesn't allow different attrs for
different fields
-+-
 Reporter:  ciantic@…|Owner:  felixxm
 Type:  New feature  |   Status:  assigned
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  SplitDateTimeWidget  | Triage Stage:  Accepted
  MultiWidget|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * 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/074.4970cc2c1f5d4c98b8363c481341c65b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27629: Inconsistent check of allow_relation in ForwardManyToOneDescriptor.set

2017-01-13 Thread Django

#27629: Inconsistent check of allow_relation in 
ForwardManyToOneDescriptor.__set__
-+-
 Reporter:  Sven Coenye  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  allow_relation   | Triage Stage:  Accepted
  ForwardManyToOneDescriptor |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Ian R-P):

 If all DATABASE_ROUTERS return None for db_for_write it takes the
 {{{hints['instance']._state.db}}} value (if one exists) and returns that
 for the parent model's own _state.db value.

 {{{
 ...\django\db\utils.py:257 def_router_func(action):

 267:chosen_db = method(model, **hints)
 268:if chosen_db:
 269:return chosen_db
 270:instance = hints.get('instance')
 271:if instance is not None and instance._state.db:
 272:return instance._state.db
 273:return DEFAULT_DB_ALIAS
 274:return _route_db
 }}}

 I was able to solve this by changing my database router from return None
 to 'default' (for the time being, as documentation says it should return
 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 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/065.565e3f514192d086eeaae9941c105b16%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27149: Allow using a subquery in QuerySet.filter()

2017-01-13 Thread Django

#27149: Allow using a subquery in QuerySet.filter()
-+-
 Reporter:  MikiSoft |Owner:  Matthew
 |  Schinckel
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  Queryset SubQuery| Triage Stage:  Ready for
  Exists |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * needs_better_patch:  1 => 0
 * 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 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.d9a720569d799fa43e3e5c5b4c2a3250%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #27733: ClearableFileInput widget renders incorrectly

2017-01-13 Thread Django

#27733: ClearableFileInput widget renders incorrectly
-+-
   Reporter:  Luca De|  Owner:  nobody
  Feo|
   Type:  Bug| Status:  new
  Component:  Forms  |Version:  1.10
   Severity:  Normal |   Keywords:  forms widgets file
   Triage Stage: |  input
  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 The `forms.widgets.ClearableFileInput` widget (used, e.g., by the admin
 app) renders as

 {{{
 EXAMPLE
 }}}

 with the `href` attribute obviously mis-generated.

 Using Django 1.10. This line seems to be the culprit:
 https://github.com/django/django/blob/1.10.5/django/forms/widgets.py#L400

--
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/048.20509a14fc616a797d6c8d1fc297da93%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27663: Make Index.create_sql() and SchemaEditor._create_index_sql() return SQL parameters as well

2017-01-13 Thread Django

#27663: Make Index.create_sql() and SchemaEditor._create_index_sql() return SQL
parameters as well
-+-
 Reporter:  Markus Holtermann|Owner:  Markus
 Type:   |  Holtermann
  Cleanup/optimization   |   Status:  assigned
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Markus Holtermann):

 And given that, I lean towards closing as wontfix or worksforme.

--
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/065.6d0b9d1402537a356f78988c470066b7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27663: Make Index.create_sql() and SchemaEditor._create_index_sql() return SQL parameters as well

2017-01-13 Thread Django

#27663: Make Index.create_sql() and SchemaEditor._create_index_sql() return SQL
parameters as well
-+-
 Reporter:  Markus Holtermann|Owner:  Markus
 Type:   |  Holtermann
  Cleanup/optimization   |   Status:  assigned
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Markus Holtermann):

 * needs_better_patch:  0 => 1
 * stage:  Ready for checkin => Accepted


Comment:

 Looking at #25809 again I noticed that `SchemaEditor.quote_value()` is
 sufficient when creating the SQL query as none of the values put through
 that function are user defined but defined at development time by
 developers.

--
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/065.b5b6824cf552c1489e87a677ac56ed59%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26056: ArrayField does not work with ValueListQuerySet

2017-01-13 Thread Django

#26056: ArrayField does not work with ValueListQuerySet
--+
 Reporter:  Przemek   |Owner:  (none)
 Type:  New feature   |   Status:  new
Component:  contrib.postgres  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  1
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Simon Charette):

 * 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/064.5932d08d36e94a295295fe142fe0b954%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27732: django.contrib.postgres.search SearchRank doesn't handle SearchVectorField references

2017-01-13 Thread Django

#27732: django.contrib.postgres.search SearchRank doesn't handle 
SearchVectorField
references
--+--
 Reporter:  Matt Hoskins  |Owner:  (none)
 Type:  Bug   |   Status:  new
Component:  contrib.postgres  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--
Changes (by Simon Charette):

 * cc: Marc Tamlyn (added)
 * version:  1.10 => master


Comment:

 Marc, any thoughts on that?

--
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/070.17200bc15b2134e0b76bf034f0c82f39%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27518: HTTP Referer leaks password reset link

2017-01-13 Thread Django

#27518: HTTP Referer leaks password reset link
-+-
 Reporter:  Romain Garrigues |Owner:  Romain
 Type:   |  Garrigues
  Cleanup/optimization   |   Status:  closed
Component:  contrib.auth |  Version:  1.10
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  password reset   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"ede59ef6f39ff8a6443c2b24df0208ef6ec41ee0" ede59ef6]:
 {{{
 #!CommitTicketReference repository=""
 revision="ede59ef6f39ff8a6443c2b24df0208ef6ec41ee0"
 Fixed #27518 -- Prevented possibie password reset token leak via HTTP
 Referer header.

 Thanks Florian Apolloner for contributing to this patch and
 Collin Anderson, Markus Holtermann, and Tim Graham for review.
 }}}

--
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/064.9292370cfb5889e1caf984722885dcbe%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27709: ContentTypes.objects.get_for_models returns inconsistent results for proxy models

2017-01-13 Thread Django

#27709: ContentTypes.objects.get_for_models returns inconsistent results for 
proxy
models
-+-
 Reporter:  Peter Inglesby   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:   |  Version:  master
  contrib.contenttypes   |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * 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 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/065.8ea12b28e340efe2e11fa0c81b0374aa%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27723: `type` is not propagated correctly to widgets in MultiWidgets

2017-01-13 Thread Django

#27723: `type` is not propagated correctly to widgets in MultiWidgets
-+
 Reporter:  felixxm  |Owner:  felixxm
 Type:  Bug  |   Status:  closed
Component:  Forms|  Version:  master
 Severity:  Release blocker  |   Resolution:  fixed
 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 Tim Graham ):

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


Comment:

 In [changeset:"974d14534ca6bc12352c08576af5628e3f042652" 974d1453]:
 {{{
 #!CommitTicketReference repository=""
 revision="974d14534ca6bc12352c08576af5628e3f042652"
 Fixed #27723 -- Set MultiWidget's subwidgets input type from attrs
 argument.

 Regression in b52c73008a9d67e9ddbb841872dc15cdd3d6ee01.
 }}}

--
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/065.013850bd67c754f6f220b181c1260ffe%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #5851: SplitDateTimeWidget (or MultiWidget) doesn't allow different attrs for different fields

2017-01-13 Thread Django

#5851: SplitDateTimeWidget (or MultiWidget) doesn't allow different attrs for
different fields
-+-
 Reporter:  ciantic@…|Owner:  felixxm
 Type:  New feature  |   Status:  assigned
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  SplitDateTimeWidget  | Triage Stage:  Accepted
  MultiWidget|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * status:  new => assigned
 * needs_docs:  1 => 0
 * owner:  nobody => felixxm
 * cc: felisiak.mariusz@… (added)


Comment:

 I think that this is a issue specific for `SplitDateTimeWidget` and
 `SplitHiddenDateTimeWidget`, because in general you can get the same
 result in a different way e.g.:

 {{{
 MultiWidget(
 widgets=(
 Input(attrs={'class': 'foo'}),
 Input(attrs={'class': 'bar'}),
 )
 )
 }}}

 IMO there is no need to complicate  `MultiWidget`.

 [https://github.com/django/django/pull/7843 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/074.6ba1ab04b4b3d5873853a0eab6104dd7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #27732: django.contrib.postgres.search SearchRank doesn't handle SearchVectorField references

2017-01-13 Thread Django

#27732: django.contrib.postgres.search SearchRank doesn't handle 
SearchVectorField
references
+
   Reporter:  matt-hoskins  |  Owner:  (none)
   Type:  Bug   | Status:  new
  Component:  contrib.postgres  |Version:  1.10
   Severity:  Normal|   Keywords:
   Triage Stage:  Unreviewed|  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+
 For search performance I'm using SearchVectorField on a model. However if
 I reference that field in the vector argument to SearchRank I get an
 error. This is because SearchRank always wraps a vector argument that
 lacks a "resolve_expression" attribute as a SearchVector even if it would
 end up resolving to a SearchVectorField.

 If I modify tests/postgres_tests/test_search.py and add the following to
 the SearchVectorFieldTest class:
 {{{#!python
 def test_existing_vector_ranking(self):
 Line.objects.update(dialogue_search_vector=SearchVector('dialogue'))
 searched = Line.objects.filter(character=self.minstrel).annotate(
 rank=SearchRank('dialogue_search_vector', SearchQuery('brave
 sir robin')),
 ).order_by('rank')
 self.assertSequenceEqual(searched, [self.verse2, self.verse1,
 self.verse0])
 }}}

 Then this results in the following error:
 {{{
 ProgrammingError: function to_tsvector(tsvector) does not exist
 LINE 1: ... "postgres_tests_line"."dialogue_config", ts_rank(to_tsvecto...
  ^
 HINT:  No function matches the given name and argument types. You might
 need to add explicit type casts.
 }}}

 As the enforced wrapping of the vector argument in a SearchVector is then
 causing the sql to wrap the tsvector field in a coalesce (which doesn't
 cause an issue) and then a to_tsvector call.

 I've not delved into the Expressions code before (my last rummaging around
 in the bowels of the query code was a few years ago) but from my quick
 look at existing code and the APIs then perhaps a solution is for
 SearchRank to not wrap the vector argument as it comes into __init__ but
 instead have a resolve_expression call which checks the first resolved
 expression on the result of calling super's resolve_expression is or isn't
 of type SearchVectorField and then if it isn't then resolve a wrapped
 version.

 I've attached a patch which both adds the test I mention above (it may be
 that it should live in the rank test rather than the search vector field
 test, or have its own test class which covers the combination of both) and
 also modifies SearchRank in the way I've suggested above. The postgres
 tests pass on my test system with this 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 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/055.dec0dc5f540ea7cd185568a67565177d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27732: django.contrib.postgres.search SearchRank doesn't handle SearchVectorField references

2017-01-13 Thread Django

#27732: django.contrib.postgres.search SearchRank doesn't handle 
SearchVectorField
references
--+--
 Reporter:  matt-hoskins  |Owner:  (none)
 Type:  Bug   |   Status:  new
Component:  contrib.postgres  |  Version:  1.10
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--
Changes (by matt-hoskins):

 * Attachment "searchrankvectorfieldfix.diff" 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/070.c857240f98842c8836cbcdc5d97d7c95%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #20483: Reduce the set of apps seen by individual tests

2017-01-13 Thread Django

#20483: Reduce the set of apps seen by individual tests
-+-
 Reporter:  Anssi Kääriäinen |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Testing framework|  Version:  master
 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:  0|UI/UX:  0
-+-

Comment (by Simon Charette ):

 In [changeset:"973cfd2ef56664480d0e1b112da51793cdf85448" 973cfd2]:
 {{{
 #!CommitTicketReference repository=""
 revision="973cfd2ef56664480d0e1b112da51793cdf85448"
 Refs #20483 -- Implemented cascaded flush on Oracle.

 The initial implementation added support for PostgreSQL but it is also
 required
 on Oracle (13b7f299de79e3eb101c3f015386eba39a8f3928).

 Thanks Mariusz Felisiak for the foreign key retreival queries.
 }}}

--
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.eb568edafed9267d8b7d77e1abf77e3d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27639: Add a chunk size argument to QuerySet.iterator()

2017-01-13 Thread Django

#27639: Add a chunk size argument to QuerySet.iterator()
-+-
 Reporter:  François Freitag |Owner:  François
 |  Freitag
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  cursors database | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * needs_better_patch:  0 => 1
 * stage:  Ready for checkin => Accepted


Comment:

 Some test failures on Oracle must be fixed.

--
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/073.8855c1c873bf5b8a63f000623f2b2bd6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27709: ContentTypes.objects.get_for_models returns inconsistent results for proxy models

2017-01-13 Thread Django

#27709: ContentTypes.objects.get_for_models returns inconsistent results for 
proxy
models
-+-
 Reporter:  Peter Inglesby   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:   |  Version:  master
  contrib.contenttypes   |
 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:  0|UI/UX:  0
-+-
Changes (by Simon Charette ):

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


Comment:

 In [changeset:"4e48cfc108c6cf69052cc728e72dc2cb25a880a5" 4e48cfc]:
 {{{
 #!CommitTicketReference repository=""
 revision="4e48cfc108c6cf69052cc728e72dc2cb25a880a5"
 Fixed #27709 -- Fixed get_for_models() for proxies with an empty cache.

 Thanks Peter Inglesby for the report and tests.
 }}}

--
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/065.1400bde1400cd8cc8ae67919603a3cd4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27732: django.contrib.postgres.search SearchRank doesn't handle SearchVectorField references

2017-01-13 Thread Django

#27732: django.contrib.postgres.search SearchRank doesn't handle 
SearchVectorField
references
--+--
 Reporter:  Matt Hoskins  |Owner:  (none)
 Type:  Bug   |   Status:  new
Component:  contrib.postgres  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--

Comment (by Marc Tamlyn):

 I had to make a choice as to the "default" behaviour of SearchRank (and
 for that matter SearchVector). I made the latter match the former - so
 that the query `SearchRank('body_text', SearchQuery('django'))` worked. I
 think supporting the simple string version in both cases (when it is or is
 not a `SearchVector`) already is somewhat confusing personally, especially
 as I believe the "work around" is:

 `SearchRank(F('dialogue_search_vector'), SearchQuery('brave sir robin'))`

--
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/070.d1dc74eddfb9a96cde3f0fea9e1250a1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #5851: SplitDateTimeWidget (or MultiWidget) doesn't allow different attrs for different fields

2017-01-13 Thread Django

#5851: SplitDateTimeWidget (or MultiWidget) doesn't allow different attrs for
different fields
-+-
 Reporter:  ciantic@…|Owner:  felixxm
 Type:  New feature  |   Status:  assigned
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  SplitDateTimeWidget  | Triage Stage:  Accepted
  MultiWidget|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|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/074.8d4ec7ad3ea5716591ccc4df20deeafe%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27732: django.contrib.postgres.search SearchRank doesn't handle SearchVectorField references

2017-01-13 Thread Django

Comment (by Matt Hoskins):

The example for SearchRank in the documentation does only shows passing in
a SearchVector() as the first argument to SearchRank and a SearchQuery()
for the second so I was a little surprised when looking at the code to
find it was behaving such that if you passed in a string for the first
argument that it assumed you'd just missed off wrapping it in a
SearchVector() rather than it potentially being a reference to a
SearchVectorField.

If SearchRank were left as is (i.e. not supporting passing in a string
which references a SearchVectorField) then I think it would be useful for
the documentation for SearchVectorField to set out the F() "work around"
as the way to use a SearchVectorField in SearchRank. E.g. just have a bit
saying "To use a SearchVectorField in SearchRank then do..." and given an
example too. It takes a little bit of figuring out otherwise (particularly
as the documentation makes no mention that you can pass in a string as the
first argument and it'll wrap it in a SearchVector for you) and I have to
admit wrapping it in F() to prevent that behaviour is not a leap I'd made
yet as most database functions in django just take field references as
strings if the type of the field is already suitable.

--
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/070.e7300ff590949ff53ac886b03e656efd%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27718: Add QuerySet.union(), intersection(), difference() (was: Add QuerySet.union(), intersect(), minus())

Re: [Django] #5851: SplitDateTimeWidget (or MultiWidget) doesn't allow different attrs for different fields

Re: [Django] #27629: Inconsistent check of allow_relation in ForwardManyToOneDescriptor.set

Re: [Django] #27149: Allow using a subquery in QuerySet.filter()

[Django] #27733: ClearableFileInput widget renders incorrectly

Re: [Django] #27663: Make Index.create_sql() and SchemaEditor._create_index_sql() return SQL parameters as well

Re: [Django] #27663: Make Index.create_sql() and SchemaEditor._create_index_sql() return SQL parameters as well

Re: [Django] #26056: ArrayField does not work with ValueListQuerySet

Re: [Django] #27732: django.contrib.postgres.search SearchRank doesn't handle SearchVectorField references

Re: [Django] #27518: HTTP Referer leaks password reset link

Re: [Django] #27709: ContentTypes.objects.get_for_models returns inconsistent results for proxy models

Re: [Django] #27723: `type` is not propagated correctly to widgets in MultiWidgets

Re: [Django] #5851: SplitDateTimeWidget (or MultiWidget) doesn't allow different attrs for different fields

[Django] #27732: django.contrib.postgres.search SearchRank doesn't handle SearchVectorField references

Re: [Django] #27732: django.contrib.postgres.search SearchRank doesn't handle SearchVectorField references

Re: [Django] #20483: Reduce the set of apps seen by individual tests

Re: [Django] #27639: Add a chunk size argument to QuerySet.iterator()

Re: [Django] #27709: ContentTypes.objects.get_for_models returns inconsistent results for proxy models

Re: [Django] #27732: django.contrib.postgres.search SearchRank doesn't handle SearchVectorField references

Re: [Django] #5851: SplitDateTimeWidget (or MultiWidget) doesn't allow different attrs for different fields

Re: [Django] #27732: django.contrib.postgres.search SearchRank doesn't handle SearchVectorField references

21 matches

Site Navigation

Mail list logo

Footer information