Re: [Django] #26608: Add a window function expression

[Django]

#26608: Add a window function expression
-+-
 Reporter:  Jamie Cockburn   |Owner:  Mads
 |  Jensen
 Type:  New feature  |   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:  0|UI/UX:  0
-+-
Changes (by Josh Smeaton):

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

Re: [Django] #28400: TransactionTestCase will truncate data created from data migration

[Django]

#28400: TransactionTestCase will truncate data created from data migration
-+-
 Reporter:  Jared Mackey |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Testing framework|  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:  tests,data-  | Triage Stage:
  migrations |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Description changed by Jared Mackey:

Old description:

> Data migrations that create data in the database do not persist after
> running tests that inherit from `TransactionTestCase`. The first test
> that runs on the database works as expected but subsequent tests do not.
>
> Here is an example migration:
>
> {{{
> def add_group_permissions(apps, schema_editor):
> for app_config in apps.get_app_configs():
> app_config.models_module = True
> create_permissions(app_config, verbosity=0)
> app_config.models_module = None
>
> Group = apps.get_model('auth', 'Group')
> Permission = apps.get_model('auth', 'Permission')
>
> group, _ = Group.objects.get_or_create(name='demo_group')
> group.permissions.clear()
> permission = Permission.objects.get(codename='existing_permission')
> group.permissions.add(permission)
>

> class Migration(migrations.Migration):
>
> dependencies = [ ]
>
> operations = [
> migrations.RunPython(add_group_permissions,
> reverse_code=migrations.RunPython.noop),
> migrations.RunPython(lambda apps, schema_editor:
> ContentType.objects.clear_cache()),   # hack to get the ContentType cache
> to clear
> ]
> }}}
>
> Here is a test case that will prove that the second test to run will fail
> with `django.contrib.auth.models.DoesNotExist: Group matching query does
> not exist.`
>
> {{{
> class TestGroupsExist(TransactionTestCase):
> """ One of these tests will fail. Which one depends on which one the
> test runner runs first. The second one to run will fail. """
> def test_group_exists_1(self):
> self.assertIsNotNone(Group.objects.get_by_natural_key('demo_group'))
>
> def test_group_exists_2(self):
> self.assertIsNotNone(Group.objects.get_by_natural_key('demo_group'))
> }}}
>
> The following log is found after the first test is ran.
>
> `TRUNCATE ... "auth_group_permissions", "auth_group", ...;; args=None`
>
> A possible solution to this is to re-run data only migrations after
> truncating the tables.

New description:

 Data migrations that create data in the database do not persist after
 running tests that inherit from `TransactionTestCase`. The first test that
 runs on the database works as expected but subsequent tests do not. I am
 filling as a bug as I would expect that data created before tests are ran
 would persist a transaction rollback during the test cases. A possible
 solution to this is to re-run data only migrations after truncating the
 tables.

 Here is an example migration:

 {{{
 def add_group_permissions(apps, schema_editor):
 for app_config in apps.get_app_configs():
 app_config.models_module = True
 create_permissions(app_config, verbosity=0)
 app_config.models_module = None

 Group = apps.get_model('auth', 'Group')
 Permission = apps.get_model('auth', 'Permission')

 group, _ = Group.objects.get_or_create(name='demo_group')
 group.permissions.clear()
 permission = Permission.objects.get(codename='existing_permission')
 group.permissions.add(permission)


 class Migration(migrations.Migration):

 dependencies = [ ]

 operations = [
 migrations.RunPython(add_group_permissions,
 reverse_code=migrations.RunPython.noop),
 migrations.RunPython(lambda apps, schema_editor:
 ContentType.objects.clear_cache()),   # hack to get the ContentType cache
 to clear
 ]
 }}}

 Here is a test case that will prove that the second test to run will fail
 with `django.contrib.auth.models.DoesNotExist: Group matching query does
 not exist.`

 {{{
 class TestGroupsExist(TransactionTestCase):
 """ One of these tests will fail. Which one depends on which one the
 test runner runs first. The second one to run will fail. """
 def test_group_exists_1(self):
 self.assertIsNotNone(Group.objects.get_by_natural_key('demo_group'))

 def test_group_exists_2(self):
 self.assertIsNotNone(Group.objects.get_by_natural_key('demo_group'))
 }}}

 The following log is found after the first test is ran.

 `TRUNCATE ... "auth_group_permissions", "auth_group", ...;; args=None`

--

-- 
Ticket URL: 

[Django] #28400: TransactionTestCase will truncate data created from data migration

[Django]

#28400: TransactionTestCase will truncate data created from data migration
-+-
   Reporter:  Jared  |  Owner:  nobody
  Mackey |
   Type:  Bug| Status:  new
  Component:  Testing|Version:  1.11
  framework  |   Keywords:  tests,data-
   Severity:  Normal |  migrations
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 Data migrations that create data in the database do not persist after
 running tests that inherit from `TransactionTestCase`. The first test that
 runs on the database works as expected but subsequent tests do not.

 Here is an example migration:

 {{{
 def add_group_permissions(apps, schema_editor):
 for app_config in apps.get_app_configs():
 app_config.models_module = True
 create_permissions(app_config, verbosity=0)
 app_config.models_module = None

 Group = apps.get_model('auth', 'Group')
 Permission = apps.get_model('auth', 'Permission')

 group, _ = Group.objects.get_or_create(name='demo_group')
 group.permissions.clear()
 permission = Permission.objects.get(codename='existing_permission')
 group.permissions.add(permission)


 class Migration(migrations.Migration):

 dependencies = [ ]

 operations = [
 migrations.RunPython(add_group_permissions,
 reverse_code=migrations.RunPython.noop),
 migrations.RunPython(lambda apps, schema_editor:
 ContentType.objects.clear_cache()),   # hack to get the ContentType cache
 to clear
 ]
 }}}

 Here is a test case that will prove that the second test to run will fail
 with `django.contrib.auth.models.DoesNotExist: Group matching query does
 not exist.`

 {{{
 class TestGroupsExist(TransactionTestCase):
 """ One of these tests will fail. Which one depends on which one the
 test runner runs first. The second one to run will fail. """
 def test_group_exists_1(self):
 self.assertIsNotNone(Group.objects.get_by_natural_key('demo_group'))

 def test_group_exists_2(self):
 self.assertIsNotNone(Group.objects.get_by_natural_key('demo_group'))
 }}}

 The following log is found after the first test is ran.

 `TRUNCATE ... "auth_group_permissions", "auth_group", ...;; args=None`

 A possible solution to this is to re-run data only migrations after
 truncating the tables.

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

Re: [Django] #28394: BaseExpression.output_field is resolved incorrectly if source expressions have directly set output_field

[Django]

#28394: BaseExpression.output_field is resolved incorrectly if source 
expressions
have directly set output_field
-+-
 Reporter:  Sergey Fedoseev  |Owner:  Sergey
 |  Fedoseev
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   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:"504ce3914fa86a58f29f5369a806f3fe56a0d59a" 504ce391]:
 {{{
 #!CommitTicketReference repository=""
 revision="504ce3914fa86a58f29f5369a806f3fe56a0d59a"
 Fixed #28394 -- Allowed setting BaseExpression.output_field (renamed from
 _output_field).
 }}}

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

Re: [Django] #28372: Admin inline JS should fire signal on add/remove to other JS can react.

[Django]

#28372: Admin inline JS should fire signal on add/remove to other JS can react.
+--
 Reporter:  Curtis Maloney  |Owner:  nobody
 Type:  New feature |   Status:  closed
Component:  contrib.admin   |  Version:  1.11
 Severity:  Normal  |   Resolution:  needsinfo
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  1
  Needs tests:  1   |  Patch needs improvement:  0
Easy pickings:  1   |UI/UX:  0
+--

Comment (by Curtis Maloney):

 Besides being jQuery custom events, no.  I didn't see them in my initial
 perusal of the code.

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

Re: [Django] #28398: Allow management command invocation to suggest commands for mistyped commands

[Django]

#28398: Allow management command invocation to suggest commands for mistyped
commands
-+-
 Reporter:  Vlada Macek  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core (Management |  Version:  1.11
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Someday/Maybe
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham):

 Since all features have development and maintenance costs, I'd like for
 others to confirm it's worth the effort before we commit to doing it.

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

Re: [Django] #28398: Allow management command invocation to suggest commands for mistyped commands

[Django]

#28398: Allow management command invocation to suggest commands for mistyped
commands
-+-
 Reporter:  Vlada Macek  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core (Management |  Version:  1.11
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Someday/Maybe
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Vlada Macek):

 Thanks for considering. I don't see this feature to require a considerable
 planning to be completed on first shot. It could evolve.
 I was thinking about similarity string search etc., but ended up with the
 simplest change possible, a substring search. This version would start to
 help me.
 Okay, adding colors wasn't the simplest, but just nice and can be removed.
 I like simple clever hints to the user like this.
 Bash completion is neat, but not always available and installed.

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

Re: [Django] #27982: Possible bug related to queryset union

[Django]

#27982: Possible bug related to queryset union
-+-
 Reporter:  gigelu   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.11
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  invalid
 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 gigelu):

 Yes, after I've added `or self.combinator` in the if clause, it does a
 `SELECT COUNT (*) FROM (... old query ...)`,  so the result is good now.

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

Re: [Django] #27982: Possible bug related to queryset union

[Django]

#27982: Possible bug related to queryset union
-+-
 Reporter:  gigelu   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.11
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  invalid
 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 Florian Apolloner):

 @gigelu: Can you check if https://github.com/django/django/pull/8769 fixes
 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 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.8736ab0a8f445c41e438d3a7f255b954%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28398: Allow management command invocation to suggest commands for mistyped commands (was: manage.py should offer candidate commands via substring search)

[Django]

#28398: Allow management command invocation to suggest commands for mistyped
commands
-+-
 Reporter:  Vlada Macek  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core (Management |  Version:  1.11
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Someday/Maybe
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:  Unreviewed => Someday/Maybe
 * easy:  1 => 0


Comment:

 I wonder if we could do something smarter than a substring search. Perhaps
 there are other libraries we could borrow ideas from. It would be
 appropriate to write the DevelopersMailingList to get feedback.

 I wonder if this isn't somewhat redundant to the
 [https://docs.djangoproject.com/en/dev/ref/django-admin/#bash-completion
 bash completion script] though.

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

Re: [Django] #28387: Disabled fields should not be considered changed in bound forms

[Django]

#28387: Disabled fields should not be considered changed in bound forms
-+-
 Reporter:  Kevin Corbin |Owner:  Srinivas
 |  Reddy Thatiparthy
 Type:  Bug  |   Status:  closed
Component:  Forms|  Version:  1.11
 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:"a3b5df8ed503ea559d2ffaca7ec0c735d98f1a38" a3b5df8]:
 {{{
 #!CommitTicketReference repository=""
 revision="a3b5df8ed503ea559d2ffaca7ec0c735d98f1a38"
 [1.11.x] Fixed #28387 -- Fixed has_changed() for disabled form fields that
 subclass it.

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

Re: [Django] #28387: Disabled fields should not be considered changed in bound forms

[Django]

#28387: Disabled fields should not be considered changed in bound forms
-+-
 Reporter:  Kevin Corbin |Owner:  Srinivas
 |  Reddy Thatiparthy
 Type:  Bug  |   Status:  closed
Component:  Forms|  Version:  1.11
 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
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"5debbdfcc84266703191e084914998e38f5f52eb" 5debbdfc]:
 {{{
 #!CommitTicketReference repository=""
 revision="5debbdfcc84266703191e084914998e38f5f52eb"
 Fixed #28387 -- Fixed has_changed() for disabled form fields that subclass
 it.
 }}}

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

Re: [Django] #28399: QuerySet.count() doesn't work on combined queries (union, intersection, difference) (was: Combined queries (UNION etc) do not properly count in the database.)

[Django]

#28399: QuerySet.count() doesn't work on combined queries (union, intersection,
difference)
-+-
 Reporter:  Florian Apolloner|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.11
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * version:  master => 1.11
 * severity:  Normal => Release blocker
 * stage:  Unreviewed => Accepted


Comment:

 I didn't realize this could be supported (see #27995). #27982 and #27990
 were duplicates.

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

Re: [Django] #28397: Remove DjangoRuntimeWarning

[Django]

#28397: Remove DjangoRuntimeWarning
--+
 Reporter:  Tim Graham|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 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 Tim Graham ):

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


Comment:

 In [changeset:"2e9ada15510e5729c331d7383fc9827e9082a8a9" 2e9ada15]:
 {{{
 #!CommitTicketReference repository=""
 revision="2e9ada15510e5729c331d7383fc9827e9082a8a9"
 Fixed #28397 -- Removed django.core.exceptions.DjangoRuntimeWarning.
 }}}

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

[Django] #28399: Combined queries (UNION etc) do not properly count in the database.

[Django]

#28399: Combined queries (UNION etc) do not properly count in the database.
-+-
   Reporter:  Florian|  Owner:  nobody
  Apolloner  |
   Type:  Bug| Status:  new
  Component:  Database   |Version:  master
  layer (models, ORM)|
   Severity:  Normal |   Keywords:
   Triage Stage: |  Has patch:  1
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 Currently combined queries do not issue COUNT(*) in the database which is
 not really efficient one wants to paginate through them.

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

Re: [Django] #24747: Allow transforms in order_by

[Django]

#24747: Allow transforms in order_by
-+-
 Reporter:  Ben Buchwald |Owner:  Matthew
 |  Wilkes
 Type:  New feature  |   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:  0|UI/UX:  0
-+-

Comment (by Matthew Wilkes):

 I know the depths of the ORM mean there's not many people who feel
 comfortable reviewing changes, but if anyone does have time to take a look
 and see if this needs more work I'd be very grateful. Happy to provide
 beer-based bribes, if that'll help.

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

Re: [Django] #28398: manage.py should offer candidate commands via substring search

[Django]

#28398: manage.py should offer candidate commands via substring search
-+-
 Reporter:  Vlada Macek  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core (Management |  Version:  1.11
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Vlada Macek):

 * Attachment "candidate-commands.diff" added.

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

Re: [Django] #28398: manage.py should offer candidate commands via substring search

[Django]

#28398: manage.py should offer candidate commands via substring search
-+-
 Reporter:  Vlada Macek  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core (Management |  Version:  1.11
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Vlada Macek):

 * Attachment "autocomplete.png" added.

 screenshot

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

[Django] #28398: manage.py should offer candidate commands via substring search

[Django]

#28398: manage.py should offer candidate commands via substring search
-+-
   Reporter:  Vlada  |  Owner:  nobody
  Macek  |
   Type:  New| Status:  new
  feature|
  Component:  Core   |Version:  1.11
  (Management commands)  |
   Severity:  Normal |   Keywords:
   Triage Stage: |  Has patch:  1
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  1
  UI/UX:  0  |
-+-
 Too often I can't remember the full mgmt command name, but can remember a
 part of it.

 A little enhancement would save me time.

 Attaching a screenshot and a patch. 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/049.e7cba40846fa62daa0ca71672f8ad224%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #28397: Remove DjangoRuntimeWarning

[Django]

#28397: Remove DjangoRuntimeWarning
+
   Reporter:  Tim Graham|  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  Core (Other)  |Version:  master
   Severity:  Normal|   Keywords:
   Triage Stage:  Accepted  |  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+
 `DjangoRuntimeWarning` doesn't seem to offer any benefit.

 [https://groups.google.com/d/topic/django-
 developers/L0DApOIlCAQ/discussion django-developers discussion]

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

Re: [Django] #28395: first() adds id field to group by clause on aggregation queries

[Django]

#28395: first() adds id field to group by clause on aggregation queries
--+
 Reporter:  John Gresty   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  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
--+
Changes (by Simon Charette):

 * component:  Database layer (models, ORM) => Documentation
 * version:  1.11 => master
 * type:  Bug => Cleanup/optimization
 * stage:  Unreviewed => Accepted


Comment:

 The `first()` method requires an ordering to be specified else it would
 return non-deterministic results hence why it's using `order_by('pk')`
 when the queryset isn't ordered.

 This is a bit similar to #10574 except the implicit ordering is added by
 `first()` and not `_meta.ordering` so I'd suggest
 [https://docs.djangoproject.com/en/1.11/topics/db/aggregation
 /#interaction-with-default-ordering-or-order-by we link to the aggregation
 section mentioning interaction with default ordering] or adjust the
 documention to account for that.

 IMHO it would have been better for `first()` to raise an exception when
 called on an unordered queryset instead of implicitly choosing `pk` but in
 your case I assume you want to either `order_by('group')` or `'value'`
 before calling `first()`.

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

Re: [Django] #23748: inspectdb should introspect autofield

[Django]

#23748: inspectdb should introspect autofield
-+-
 Reporter:  Paul Dejean  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  inspectdb| Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham):

 It looks like the remaining task for this ticket is to add introspection
 on SQLite (if the column definition includes AUTOINCREMENT).

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

Re: [Django] #28396: filter_horizontal and filter_vertical do not scroll horizontally for long string representations

[Django]

#28396: filter_horizontal and filter_vertical do not scroll horizontally for 
long
string representations
-+-
 Reporter:  Foo Chuan Wei|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:  admin,   | Triage Stage:
  filter_horizontal, |  Unreviewed
  filter_vertical|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-

Comment (by Tim Graham):

 This was addressed in #20821 by adding tooltips so you can hover over the
 choice to see the full name. I think it's good enough. 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/069.a54f8f09fc6e75fe00fe0ad7d2b98076%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28264: forms.FilePathField does not return sorted subdirectories in formfield

[Django]

#28264: forms.FilePathField does not return sorted subdirectories in formfield
-+-
 Reporter:  Jean-Marie Thomas|Owner:  Srinivas
 Type:   |  Reddy Thatiparthy
  Cleanup/optimization   |   Status:  assigned
Component:  Forms|  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:  FilePathField| 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
 * needs_tests:  1 => 0


Comment:

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

Re: [Django] #28396: filter_horizontal and filter_vertical do not scroll horizontally for long string representations

[Django]

#28396: filter_horizontal and filter_vertical do not scroll horizontally for 
long
string representations
-+-
 Reporter:  Foo Chuan Wei|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:  admin,   | Triage Stage:
  filter_horizontal, |  Unreviewed
  filter_vertical|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Description changed by Foo Chuan Wei:

Old description:

> Long string representations of models appear truncated when using
> filter_horizontal or filter_vertical in the admin, because the "filter
> interface" does not scroll horizontally.
> (See attachments).

New description:

 Long string representations of models appear truncated when using
 filter_horizontal or filter_vertical in the admin, because the "filter
 interface" does not scroll horizontally.

 For filter_horizontal:
 [[Image(filter_horizontal.png)]]

 For filter_vertical:
 [[Image(filter_vertical.png)]]

--

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

Re: [Django] #28396: filter_horizontal and filter_vertical do not scroll horizontally for long string representations

[Django]

#28396: filter_horizontal and filter_vertical do not scroll horizontally for 
long
string representations
-+-
 Reporter:  foochuanwei  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:  admin,   | Triage Stage:
  filter_horizontal, |  Unreviewed
  filter_vertical|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Description changed by foochuanwei:

Old description:

> Long string representations of models appear truncated when using
> filter_horizontal or filter_vertical in the admin, because the "filter
> interface" does not scroll horizontally.

New description:

 Long string representations of models appear truncated when using
 filter_horizontal or filter_vertical in the admin, because the "filter
 interface" does not scroll horizontally.
 (See attachments).

--

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

Re: [Django] #28396: filter_horizontal and filter_vertical do not scroll horizontally for long string representations

[Django]

#28396: filter_horizontal and filter_vertical do not scroll horizontally for 
long
string representations
-+-
 Reporter:  Foo Chuan Wei|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:  admin,   | Triage Stage:
  filter_horizontal, |  Unreviewed
  filter_vertical|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Changes (by Foo Chuan Wei):

 * Attachment "filter_vertical.png" added.

 filter_vertical does not scroll horizontally for long strings

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

Re: [Django] #28396: filter_horizontal and filter_vertical do not scroll horizontally for long string representations

[Django]

#28396: filter_horizontal and filter_vertical do not scroll horizontally for 
long
string representations
-+-
 Reporter:  Foo Chuan Wei|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:  admin,   | Triage Stage:
  filter_horizontal, |  Unreviewed
  filter_vertical|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Changes (by Foo Chuan Wei):

 * Attachment "filter_horizontal.png" added.

 filter_horizontal does not scroll horizontally for long strings

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

Re: [Django] #28388: JSONField cannot be overridden to use OrderedDict as python-representation of objects of JSON

[Django]

#28388: JSONField cannot be overridden to use OrderedDict as 
python-representation
of objects of JSON
--+--
 Reporter:  Vladimir Chub |Owner:  (none)
 Type:  New feature   |   Status:  closed
Component:  contrib.postgres  |  Version:  1.11
 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 Tim Graham):

 I'm not sure. You could try to implement it and then write to the
 DevelopersMailingList with the proposal.

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

[Django] #28396: filter_horizontal and filter_vertical do not scroll horizontally for long string representations

[Django]

#28396: filter_horizontal and filter_vertical do not scroll horizontally for 
long
string representations
-+-
   Reporter:  Foo Chuan  |  Owner:  nobody
  Wei|
   Type:  Bug| Status:  new
  Component: |Version:  1.11
  contrib.admin  |   Keywords:  admin,
   Severity:  Normal |  filter_horizontal, filter_vertical
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  1  |
-+-
 Long string representations of models appear truncated when using
 filter_horizontal or filter_vertical in the admin, because the "filter
 interface" does not scroll horizontally.

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

[Django] #28395: first() adds id field to group by clause on aggregation queries

[Django]

#28395: first() adds id field to group by clause on aggregation queries
-+-
   Reporter:  John   |  Owner:  nobody
  Gresty |
   Type:  Bug| Status:  new
  Component:  Database   |Version:  1.11
  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  |
-+-
 When evaluating an aggregation query, for example:

 {{{
 MyModel.objects.values('group').annotate(value=Sum('value'))
 }}}

 works as expected. However adding {{{first()}}} to the end will add the id
 field into the resulting queryset and as such the annotated value will be
 the value of the first row, instead of the sum of the group.


 {{{
 >>> MyModel.objects.create(value=10)
 
 >>> MyModel.objects.create(value=20)
 
 >>> MyModel.objects.values('group').annotate(value=Sum('value'))
 
 >>> MyModel.objects.values('group').annotate(value=Sum('value')).first()
 {'group': 0, 'value': 10}
 }}}

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

Re: [Django] #28388: JSONField cannot be overridden to use OrderedDict as python-representation of objects of JSON

[Django]

#28388: JSONField cannot be overridden to use OrderedDict as 
python-representation
of objects of JSON
--+--
 Reporter:  Vladimir Chub |Owner:  (none)
 Type:  New feature   |   Status:  closed
Component:  contrib.postgres  |  Version:  1.11
 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 Vladimir Chub):

 >Perhaps there are other custom fields that use the PostgreSQL's json
 datatype (which does preserve ordering) that will work for your use case.

 Of course there is a `json` field in PostgreSQl supporting ordering
 https://www.postgresql.org/docs/9.6/static/datatype-json.html

 >Because the json type stores an exact copy of the input text, it will
 preserve semantically-insignificant white space between tokens, as well as
 the order of keys within JSON objects

 Django is now using `jsonrb` as JSONField, but also something like
 OrderedJSONField mapped with PostgreSQL `json` field can be implemented.
 Are there any chances of if?

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

Re: [Django] #23748: inspectdb should introspect autofield

[Django]

#23748: inspectdb should introspect autofield
-+-
 Reporter:  Paul Dejean  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  inspectdb| Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * version:  1.7 => master


Comment:

 In
 
[https://github.com/django/django/commit/9af6c97504ef2b06dd5292d03ea94d3eb5d8c4d6
 9af6c97504ef2b06dd5292d03ea94d3eb5d8c4d6]

 Added AutoField introspection on Oracle.

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