Re: [Django] #29991: Document logger propagation for the default logging config

[Django]

#29991: Document logger propagation for the default logging config
-+-
 Reporter:  George Tantiras  |Owner:  George
 Type:   |  Tantiras
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  2.1
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  Logger   | 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 Tim Graham ):

 In [changeset:"8f8be2a8d72643592d697317268e85e7887f2bbf" 8f8be2a8]:
 {{{
 #!CommitTicketReference repository=""
 revision="8f8be2a8d72643592d697317268e85e7887f2bbf"
 [2.1.x] Fixed #29991 -- Doc'd logger propogation for the default logging
 config.

 Backport of 793a71b7be9970bee8cbac68985684628e99ad23 from master.
 }}}

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

Re: [Django] #29991: Document logger propagation for the default logging config

[Django]

#29991: Document logger propagation for the default logging config
-+-
 Reporter:  George Tantiras  |Owner:  George
 Type:   |  Tantiras
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  2.1
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  Logger   | 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:"793a71b7be9970bee8cbac68985684628e99ad23" 793a71b]:
 {{{
 #!CommitTicketReference repository=""
 revision="793a71b7be9970bee8cbac68985684628e99ad23"
 Fixed #29991 -- Doc'd logger propogation for the default logging config.
 }}}

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

Re: [Django] #25678: migrate scalar to array field in PostrgreSQL fails

[Django]

#25678: migrate scalar to array field in PostrgreSQL fails
-+-
 Reporter:  Mark Mikofski|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  PostgreSQL,  | Triage Stage:  Accepted
  ArrayField |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mark Mikofski):

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


Comment:

 this was fixed in #25002 in
 
[https://github.com/django/django/blob/73040e584a9ccc770593a3885f5fe40fda142e0d/django/db/backends/postgresql_psycopg2/schema.py#L8
 postgresql.schema.py:8] by
 
[https://github.com/django/django/commit/73040e584a9ccc770593a3885f5fe40fda142e0d
 commit 73040e58] 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.4bcc9dd2c509b65427770abd55a80717%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29991: Document logger propagation for the default logging config (was: Explain the default logging configuration a bit more)

[Django]

#29991: Document logger propagation for the default logging config
-+-
 Reporter:  George Tantiras  |Owner:  George
 Type:   |  Tantiras
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  2.1
 Severity:  Normal   |   Resolution:
 Keywords:  Logger   | 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/066.6bbfbb2c566523d9fe622a1765eb3427%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29984: Support prefetch_related() with Queryset.iterator()

[Django]

#29984: Support prefetch_related() with Queryset.iterator()
-+-
 Reporter:  Taylor H |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  2.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Raphael Kimmig):

 I've created a proof of concept implementation
 https://github.com/django/django/pull/10707/

 I think prefetching is probably closer to what a user would expect from
 the api.

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

Re: [Django] #29997: Allow combining SearchQuerys with different configs

[Django]

#29997: Allow combining SearchQuerys with different configs
-+-
 Reporter:  Jaap Roes|Owner:  Jaap Roes
 Type:  Bug  |   Status:  assigned
Component:  contrib.postgres |  Version:  1.11
 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):

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


Comment:

 Before merging, I'll give the original author some time to respond to the
 question about why the restriction was added. The patch looks fine.

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

Re: [Django] #6870: pre_delete should be sent before collecting ForeignKey relationships

[Django]

#6870: pre_delete should be sent before collecting ForeignKey relationships
-+-
 Reporter:  Waldemar Kornewald   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  pre_delete signals   | Triage Stage:  Accepted
  related|
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tiedye):

 Will this be addressed at any point?  I've been running into this issue
 for the past month.

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

Re: [Django] #29997: Allow combining SearchQuerys with different configs

[Django]

#29997: Allow combining SearchQuerys with different configs
--+-
 Reporter:  Jaap Roes |Owner:  Jaap Roes
 Type:  Bug   |   Status:  assigned
Component:  contrib.postgres  |  Version:  1.11
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+-
Changes (by Simon Charette):

 * version:  master => 1.11
 * component:  Database layer (models, ORM) => contrib.postgres


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

Re: [Django] #29997: Allow combining SearchQuerys with different configs

[Django]

#29997: Allow combining SearchQuerys with different configs
-+-
 Reporter:  Jaap Roes|Owner:  Jaap Roes
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Simon Charette):

 * stage:  Unreviewed => Accepted


Comment:

 Thanks for the bisect sleuthing here. Given this is a regression in 1.11
 I'm not sure this qualifies for a backport for 2.1 at this point.

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

Re: [Django] #25251: Inconsistent availability of data migrations in TransactionTestCase when using --keepdb

[Django]

#25251: Inconsistent availability of data migrations in TransactionTestCase when
using --keepdb
-+-
 Reporter:  David Szotten|Owner:  Romain
 |  Garrigues
 Type:  Bug  |   Status:  closed
Component:  Testing framework|  Version:  1.8
 Severity:  Normal   |   Resolution:  fixed
 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 Tim Graham ):

 In [changeset:"9fa0d3786febf36c87ef059a39115aa1ce3326e8" 9fa0d37]:
 {{{
 #!CommitTicketReference repository=""
 revision="9fa0d3786febf36c87ef059a39115aa1ce3326e8"
 Refs #25251 -- Filtered out skipped tests when processing the test suite
 to set _next_serialized_rollback.
 }}}

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

Re: [Django] #29997: Allow combining SearchQuerys with different configs

[Django]

#29997: Allow combining SearchQuerys with different configs
-+-
 Reporter:  Jaap Roes|Owner:  Jaap Roes
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Jaap Roes):

 * type:  Cleanup/optimization => Bug


Comment:

 I ran `git bisect` and technically this is a regression from commit
 978a00e39fee25cfa99065285b0de88366710fad

 Before that commit this works:

 `search.SearchQuery("foo", config="simple") | search.SearchQuery("bar",
 config="english")`

 Afterwards it doesn't

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

Re: [Django] #29998: pk setup for MTI to parent get confused by multiple OneToOne references.

[Django]

#29998: pk setup for MTI to parent get confused by multiple OneToOne references.
-+-
 Reporter:  Mārtiņš Šulcs|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  2.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mārtiņš Šulcs):

 Replying to [comment:1 Simon Charette]:

 It does go away primary_key.
 Why is parent_link even necessary in that case? Having pk OneToOne with to
 MTI child should imply it's parent link.

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

Re: [Django] #29998: pk setup for MTI to parent get confused by multiple OneToOne references.

[Django]

#29998: pk setup for MTI to parent get confused by multiple OneToOne references.
-+-
 Reporter:  Mārtiņš Šulcs|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  2.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Simon Charette):

 * stage:  Unreviewed => Accepted


Comment:

 That seems to be a bug, managed to reproduce.

 Does the error go away if you add `primary_key=True` to `document_ptr`
 like I assume you wanted to do? This makes me realized that the
 [https://docs.djangoproject.com/en/2.1/topics/db/models/#multi-table-
 inheritance MTI documentation] is not completely correcy,
 
[https://github.com/django/django/blob/7d1123e5ada60963ba3c708a8932e57342278706/django/db/models/options.py#L225-L244
 the automatically added `place_ptr` field end up with `primary_key=True`].

 Not sure why we're not checking `and field.remote_field.parent_link` on
 
[https://github.com/django/django/blob/7d1123e5ada60963ba3c708a8932e57342278706/django/db/models/base.py#L183
 parent links connection].

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

Re: [Django] #29992: Error in admin checking list_display items

[Django]

#29992: Error in admin checking list_display items
--+--
 Reporter:  Giovanni Toffoli  |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  contrib.admin |  Version:  2.1
 Severity:  Release blocker   |   Resolution:  needsinfo
 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 Tim Graham):

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


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

Re: [Django] #29990: Error in part 7 of the tutorial

[Django]

#29990: Error in part 7 of the tutorial
---+--
 Reporter:  Shrey  |Owner:  Shrey
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  2.1
 Severity:  Normal |   Resolution:  invalid
 Keywords:  documentation  | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--

Comment (by Shrey):

 Yep. Now I see that it was a mistake made by me. And if the docs were to
 be updated the name mysite would be used instead of basic.

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

Re: [Django] #29997: Allow combining SearchQuerys with different configs

[Django]

#29997: Allow combining SearchQuerys with different configs
-+-
 Reporter:  Jaap Roes|Owner:  Jaap Roes
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Jaap Roes):

 * owner:  nobody => Jaap Roes


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

[Django] #29998: pk setup for MTI to parent get confused by multiple OneToOne references.

[Django]

#29998: pk setup for MTI to parent get confused by multiple OneToOne references.
-+-
   Reporter:  shulcsm|  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Database   |Version:  2.1
  layer (models, ORM)|
   Severity:  Normal |   Keywords:
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 {{{
 class Document(models.Model):
 pass

 class Picking(Document):
 document_ptr = models.OneToOneField(Document,
 on_delete=models.CASCADE, parent_link=True, related_name='+')
 origin = models.OneToOneField(Document, related_name='picking',
 on_delete=models.PROTECT)
 }}}

 produces django.core.exceptions.ImproperlyConfigured: Add parent_link=True
 to appname.Picking.origin.

 {{{
 class Picking(Document):
 origin = models.OneToOneField(Document, related_name='picking',
 on_delete=models.PROTECT)
 document_ptr = models.OneToOneField(Document,
 on_delete=models.CASCADE, parent_link=True, related_name='+')
 }}}
 Works

 First issue is that order seems to matter?
 Even if ordering is required "by design"(It shouldn't be we have explicit
 parent_link marker) shouldn't it look from top to bottom like it does with
 managers and other things?

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

[Django] #29997: Allow combining SearchQuerys with different configs

[Django]

#29997: Allow combining SearchQuerys with different configs
-+-
   Reporter:  Jaap Roes  |  Owner:  nobody
   Type: | Status:  assigned
  Cleanup/optimization   |
  Component:  Database   |Version:  master
  layer (models, ORM)|
   Severity:  Normal |   Keywords:
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 The fix for ticket #27143 (SearchQuery is not combinable using more than
 one `&` or `|` operators) introduced some code that raises a `TypeError`
 when trying to combine `SearchQuery` objects that do not share the same
 `config`.

 I'm not sure if this restriction makes sense. In SQL it seems to be
 allowed e.g.:

 `SELECT to_tsquery('simple', 'working') || to_tsquery('english',
 'working');`
 `'working' | 'work'`

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

Re: [Django] #29992: Error in admin checking list_display items

[Django]

#29992: Error in admin checking list_display items
-+--
 Reporter:  gtoffoli |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  2.1
 Severity:  Release blocker  |   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 gtoffoli):

 You are right. I created a new project for testing, starting with that
 excerpt; then added some more stuff, without being able to reproduce the
 problem.
 I don't know what, in the real project, interferes with the creation of
 admin classes. When I can, I'll keep adding stuff to the test project.
 For the moment I will use a patched version of the admin.check module.

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