Re: [Django] #32046: Add a postgres operation to create collations.

[Django]

#32046: Add a postgres operation to create collations.
--+---
 Reporter:  Tom Carrick   |Owner:  Tom Carrick
 Type:  New feature   |   Status:  assigned
Component:  contrib.postgres  |  Version:  master
 Severity:  Normal|   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 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/065.4a89d534890fdbf834e68a96885d8d3d%40djangoproject.com.

Re: [Django] #29899: Adapt the auto-detector to detect changes from model states instead of model classes

[Django]

#29899: Adapt the auto-detector to detect changes from model states instead of
model classes
-+-
 Reporter:  Simon Charette   |Owner:  David
 Type:   |  Wobrock
  Cleanup/optimization   |   Status:  assigned
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   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 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/067.e08b5d07fd8287369c21f2afffa50d93%40djangoproject.com.

Re: [Django] #31653: Add PostgreSQL operations to add constraints via NOT VALID / VALIDATE CONSTRAINT

[Django]

#31653: Add PostgreSQL operations to add constraints via NOT VALID / VALIDATE
CONSTRAINT
-+-
 Reporter:  Adam (Chainz)|Owner:  nobody
  Johnson|
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  contrib.postgres |  Version:  master
 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 Adam (Chainz) Johnson):

 I think it would be better to keep the SQL modification purely in the
 operation class. It's only for PostgreSQL, so it doesn't need to be part
 of the more generic backend class.

-- 
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/068.45ccbd9ac8e4a58703066597a6ed0d19%40djangoproject.com.

Re: [Django] #31672: debug error view shows no traceback if exc.__traceback__ is None for innermost exception

[Django]

#31672: debug error view shows no traceback if exc.__traceback__ is None for
innermost exception
-+-
 Reporter:  Chris Jerdonek   |Owner:  Hasan
 Type:   |  Ramezani
  Cleanup/optimization   |   Status:  new
Component:  Error reporting  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
  technical_500_response,traceback,chain|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"a492ccf0bc3da0b99c27b44e491ec3d6aabd5d3f" a492ccf0]:
 {{{
 #!CommitTicketReference repository=""
 revision="a492ccf0bc3da0b99c27b44e491ec3d6aabd5d3f"
 Refs #31672 -- Simplified ExceptionReporter.get_traceback_frames().
 }}}

-- 
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/067.53c71a39cb7d2d4de57c46f6f0940a92%40djangoproject.com.

Re: [Django] #25253: MySQL migrations drop & recreate constraints unnecessarily when changing attributes that don't affect the schema

[Django]

#25253: MySQL migrations drop & recreate constraints unnecessarily when changing
attributes that don't affect the schema
-+-
 Reporter:  Thomas Recouvreux|Owner:  Çağıl
 Type:   |  Uluşahin
  Cleanup/optimization   |   Status:  closed
Component:  Migrations   |  Version:  2.1
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  migrations m2m   | Triage Stage:  Ready for
  mysql  |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak ):

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


Comment:

 In [changeset:"9159d173c3822312c653db7ff5b9a94b14af1dca" 9159d17]:
 {{{
 #!CommitTicketReference repository=""
 revision="9159d173c3822312c653db7ff5b9a94b14af1dca"
 Fixed #25253 -- Made AlterField operation a noop when changing attributes
 that don't affect the schema.
 }}}

-- 
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.f2d57015538877d745fa287774280776%40djangoproject.com.

Re: [Django] #32089: prefetch_related_objects() does not work for reused model instances.

[Django]

#32089: prefetch_related_objects() does not work for reused model instances.
-+-
 Reporter:  Dennis Kliban|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  2.2
  (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 Adam (Chainz) Johnson):

 I had a brief look at fixing this. I think it's possible by filtering the
 objects before trying to prefetch for them. See
 
https://github.com/adamchainz/django/commit/bc2991c0908abbf4973cbb48500dea4bbd6f
 . This currently fails three prefetch tests - one for executing an extra
 query, two for executing one fewer query (which may actually represent a
 true optimization).

-- 
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/065.908686d0609b5c46bdc94a01aeb4655c%40djangoproject.com.

Re: [Django] #30022: Doc how to combine post_save signal with on_commit to alter a m2m relation when saving a model instance

[Django]

#30022: Doc how to combine post_save signal with on_commit to alter a m2m 
relation
when saving a model instance
-+-
 Reporter:  George Tantiras  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  2.1
 Severity:  Normal   |   Resolution:  wontfix
 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 George Tantiras):

 Thank you, it is amazing what Django can do!

-- 
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.5e7b392499809dd591fd835d923a6308%40djangoproject.com.

[Django] #32111: Django 3.1.2 JSONField handling error with an Postgres Foreign Data Wrapper-based model

[Django]

#32111: Django 3.1.2 JSONField handling error with an Postgres Foreign Data
Wrapper-based model
-+-
   Reporter:  Shaheed|  Owner:  nobody
  Haque  |
   Type:  Bug| Status:  new
  Component:  Database   |Version:  3.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  |
-+-
 Over at https://groups.google.com/g/django-users/c/Sr1TDVRpCLE, it was
 suggested that I post an issue here...

 I have a Django model working fine under Django 3.0 (i.e. "Django<3.1")
 which looks like this:

 {{{
 class Job(models.Model):
 id = models.CharField(max_length=36, primary_key=True)
 queue = models.CharField(max_length=40)
 args = JSONField()
 kwargs = JSONField()
 type = models.CharField(max_length=80)
 ...

 class Meta:
 managed = False  # <--   The table is implemented as a
 Postgres FDW wrapper.
 db_table = 'jobs'
 }}}


 I am testing the update to Django 3.1.2 and hit an error in executing this
 line:

 jobs = list(models.Job.objects.filter(queue='celery',
 state='scheduled'))

 The error is as follows from pytest (i.e. stack trace with local variables
 too):

 {{{
 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
 _ _ _
 /usr/local/lib/python3.8/dist-packages/django/db/models/query.py:287: in
 __iter__
self._fetch_all()
self   = 
 /usr/local/lib/python3.8/dist-packages/django/db/models/query.py:1308: in
 _fetch_all
self._result_cache = list(self._iterable_class(self))
self   = 
 /usr/local/lib/python3.8/dist-packages/django/db/models/query.py:70: in
 __iter__
for row in compiler.results_iter(results):
annotation_col_map = {}
compiler   = 
db = 'fdw'
init_list  = ['id', 'queue', 'args', 'kwargs', 'type', 'state',
 ...]
klass_info = {'model': ,
 'select_fields': [0, 1, 2, 3, 4, 5, ...]}
known_related_objects = []
model_cls  = 
model_fields_end = 9
model_fields_start = 0
queryset   = 
related_populators = []
results= [[('8f4ab6b0-914f-4a75-972d-febbe55011fc', 'celery',
 ['paiyroll.tasks', 'call_to_string', 'call_to_string', [], {}], {},
 'paiyroll.tasks.function_run', 'scheduled', ...)]]
select = [(Col(jobs, paiyroll.Job.id), ('"jobs"."id"', []),
 None), (Col(jobs, paiyroll.Job.queue), ('"jobs"."queue"', []), None...,
 paiyroll.Job.type), ('"jobs"."type"', []), None), (Col(jobs,
 paiyroll.Job.state), ('"jobs"."state"', []), None), ...]
select_fields = [0, 1, 2, 3, 4, 5, ...]
self   = 
 /usr/local/lib/python3.8/dist-
 packages/django/db/models/sql/compiler.py:1100: in apply_converters
value = converter(value, expression, connection)
connection = 
converter  = >
converters = [(2, ([>], Col(jobs,
 pa...NField.from_db_value of
 >], Col(jobs,
 paiyroll.Job.details)))]
convs  = [>]
expression = Col(jobs, paiyroll.Job.args)
pos= 2
row= ['8f4ab6b0-914f-4a75-972d-febbe55011fc', 'celery',
 ['paiyroll.tasks', 'call_to_string', 'call_to_string', [], {}], {},
 'paiyroll.tasks.function_run', 'scheduled', ...]
rows   = 
self   = 
value  = ['paiyroll.tasks', 'call_to_string', 'call_to_string',
 [], {}]
 /usr/local/lib/python3.8/dist-packages/django/db/models/fields/json.py:74:
 in from_db_value
return json.loads(value, cls=self.decoder)
connection = 
expression = Col(jobs, paiyroll.Job.args)
self   = 
value  = ['paiyroll.tasks', 'call_to_string', 'call_to_string',
 [], {}]
 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
 _ _ _

 s = ['paiyroll.tasks', 'call_to_string', 'call_to_string', [], {}], cls =
 None
 object_hook = None, parse_float = None, parse_int = None, parse_constant =
 None
 object_pairs_hook = None, kw = {}

def loads(s, *, cls=None, object_hook=None, parse_float=None,
parse_int=None, parse_constant=None, object_pairs_hook=None,
 **kw):
"""Deserialize ``s`` (a ``str``, ``bytes`` or ``bytearray``
 instance
containing a JSON document) to a Python object.

``object_hook`` is an optional function that will be called with
 the
result of any object literal decode (a ``dict``). The return value
 of
``object_hook`` will be used instead of the ``dict``. This feature
   

Re: [Django] #32095: update_or_create should utilize update_fields on update

[Django]

#32095: update_or_create should utilize update_fields on update
-+-
 Reporter:  Florian Apolloner|Owner:  Florian
 Type:   |  Apolloner
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  3.1
  (models, ORM)  |
 Severity:  Normal   |   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 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.f7142f40ed01284d3b7ea827d760e0ab%40djangoproject.com.

Re: [Django] #25253: MySQL migrations drop & recreate constraints unnecessarily when changing attributes that don't affect the schema

[Django]

#25253: MySQL migrations drop & recreate constraints unnecessarily when changing
attributes that don't affect the schema
-+-
 Reporter:  Thomas Recouvreux|Owner:  Çağıl
 Type:   |  Uluşahin
  Cleanup/optimization   |   Status:  assigned
Component:  Migrations   |  Version:  2.1
 Severity:  Normal   |   Resolution:
 Keywords:  migrations m2m   | Triage Stage:  Ready for
  mysql  |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.f0c0ac94c72c30c3e56b15dd113d41c1%40djangoproject.com.

Re: [Django] #32110: Allow using an Enum class in form Field choices

[Django]

#32110: Allow using an Enum class in form Field choices
--+
 Reporter:  Claude Paroz  |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  Forms |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by Claude Paroz):

 I'm not so sure if this is already supported or not. But let's add some
 tests for that and they will tell us!

-- 
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/065.b625af8974f4c9ced75978e9b281d2f8%40djangoproject.com.

Re: [Django] #32110: Allow using an Enum class in form Field choices

[Django]

#32110: Allow using an Enum class in form Field choices
--+
 Reporter:  Claude Paroz  |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  Forms |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by Nick Pope):

 * easy:  0 => 1
 * stage:  Unreviewed => Accepted


Comment:

 As we use `.choices` on the enum classes to return a list of tuples there
 isn't really any code to add to make this work AFAICT.

 So this perhaps could just be documented for forms pointing to the
 documentation at
 https://docs.djangoproject.com/en/stable/ref/models/fields/#field-choices-
 enum-types

-- 
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/065.08ff26a086060a224241935e65f996df%40djangoproject.com.

Re: [Django] #29988: Use f-strings for string formatting once support for Python 3.5 is dropped

[Django]

#29988: Use f-strings for string formatting once support for Python 3.5 is 
dropped
-+-
 Reporter:  Jaap Roes|Owner:  Carlton
 Type:   |  Gibson
  Cleanup/optimization   |   Status:  closed
Component:  Core (Other) |  Version:
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  fstrings python3.6   | 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 Carlton Gibson ):

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


Comment:

 In [changeset:"411cc0ae18aa9c64447eed229e65e092d23f80e6" 411cc0a]:
 {{{
 #!CommitTicketReference repository=""
 revision="411cc0ae18aa9c64447eed229e65e092d23f80e6"
 Fixed #29988 -- Updated coding style to allow f-strings.

 Thanks to Nick Pope 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.ba040698032c6e7672c78e06a818c030%40djangoproject.com.

Re: [Django] #32109: Cannot add content to admin sidebar without breaking layout

[Django]

#32109: Cannot add content to admin sidebar without breaking layout
-+-
 Reporter:  Ben Davis|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  3.1
 Severity:  Normal   |   Resolution:
 Keywords:  admin sidebar| Triage Stage:
  template   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Carlton Gibson):

 Hi Ben.

 This is a curious one.

 Have a look at this diff:

 {{{
 $ git diff
 diff --git a/django/contrib/admin/templates/admin/index.html
 b/django/contrib/admin/templates/admin/index.html
 index b6e84b64ed..f075aef37f 100644
 --- a/django/contrib/admin/templates/admin/index.html
 +++ b/django/contrib/admin/templates/admin/index.html
 @@ -18,8 +18,22 @@
  {% endblock %}

  {% block sidebar %}
 +
 +
 +On top
 +the float and clear lets us position OK.
 +No styling.
 +
 +
 +
  
 +Inside #content-related
 +In the grey sidebar.
 +But style mismatch
 +
  
 +Inside #recent-actions-module
 +Picks up styling from Recent Actions.
  {% translate 'Recent actions' %}
  {% translate 'My actions' %}
  {% load log %}
 @@ -47,4 +61,7 @@
  {% endif %}
  
  
 +After all existing content
 +Ends up under the app list.
 +
  {% endblock %}
 }}}

 There's three ''obvious'' positions for extra content in the sidebar:

 1. Right at the top, outside `#content-related` (Bottom is in the diff
 but...)
 2. Inside `#content-related` (top or bottom)
 3. Inside `#recent-actions-module` (again top or bottom)

 If it's 1. I'm inclined to think ''Just use CSS and a clearing div to put
 it in the right place''.

 Number 2. is your suggestion from the PR, but if you put it in 3, you get
 the styling from the Recent Actions module for free.

 So I'm a bit 樂 — what do you think?

 (Half inclined to say that we should pull the inner HTML of #recent-
 actions-module into an included template to allow folks to go for whatever
 option they want here quite easily.)

-- 
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/068.6a6be560ad627e8b0f68b14ca05d6079%40djangoproject.com.

[Django] #32110: Allow using an Enum class in form Field choices

[Django]

#32110: Allow using an Enum class in form Field choices
+
   Reporter:  Claude Paroz  |  Owner:  nobody
   Type:  New feature   | Status:  new
  Component:  Forms |Version:  master
   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 |
+
 Similarly to what was done for model fields, it would be nice to have the
 `choices` widget attribute also support enum data.

-- 
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/050.5e97824f63a4aa16f7e5d906e3f5739d%40djangoproject.com.

Re: [Django] #6517: MySQL: manage.py dbshell does not get charset from DATABASES setting

[Django]

#6517: MySQL: manage.py dbshell does not get charset from DATABASES setting
-+-
 Reporter:  Tom Vergote  |Owner:  Manav
 |  Agarwal
 Type:  Bug  |   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


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/062.587bc6104c943fb1ab6afecffbcbd182%40djangoproject.com.