Re: [Django] #30413: admin_views.test_multidb fails with persistent test SQLite database.

[Django]

#30413: admin_views.test_multidb fails with persistent test SQLite database.
-+-
 Reporter:  Daniel Hahler|Owner:  Ngalim
 |  Siregar
 Type:  Bug  |   Status:  assigned
Component:  Testing framework|  Version:  master
 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
-+-
Description changed by felixxm:

Old description:

> I've tried using persistent SQLite databases for the tests (to make use
> of
> `--keepdb`), but at least some
> tsbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
> + export PATHest fails with:
>
> > sqlite3.OperationalError: database is locked
>
> This is not an issue when only using `TEST["NAME"]` with "default" (which
> is good enough in terms of performance).
>
> {{{
> diff --git i/tests/test_sqlite.py w/tests/test_sqlite.py
> index f1b65f7d01..9ce4e32e14 100644
> --- i/tests/test_sqlite.py
> +++ w/tests/test_sqlite.py
> @@ -15,9 +15,15 @@
>  DATABASES = {
>  'default': {
>  'ENGINE': 'django.db.backends.sqlite3',
> +'TEST': {
> +'NAME': 'test_default.sqlite3'
> +},
>  },
>  'other': {
>  'ENGINE': 'django.db.backends.sqlite3',
> +'TEST': {
> +'NAME': 'test_other.sqlite3'
> +},
>  }
>  }
> }}}
>
> {{{
> % tests/runtests.py admin_views.test_multidb -v 3 --keepdb --parallel 1
> …
> Operations to perform:
>   Synchronize unmigrated apps: admin_views, auth, contenttypes, messages,
> sessions, staticfiles
>   Apply all migrations: admin, sites
> Running pre-migrate handlers for application contenttypes
> Running pre-migrate handlers for application auth
> Running pre-migrate handlers for application sites
> Running pre-migrate handlers for application sessions
> Running pre-migrate handlers for application admin
> Running pre-migrate handlers for application admin_views
> Synchronizing apps without migrations:
>   Creating tables...
> Running deferred SQL...
> Running migrations:
>   No migrations to apply.
> Running post-migrate handlers for application contenttypes
> Running post-migrate handlers for application auth
> Running post-migrate handlers for application sites
> Running post-migrate handlers for application sessions
> Running post-migrate handlers for application admin
> Running post-migrate handlers for application admin_views
> System check identified no issues (0 silenced).
> ERROR
>
> ==
> ERROR: setUpClass (admin_views.test_multidb.MultiDatabaseTests)
> --
> Traceback (most recent call last):
>   File "…/Vcs/django/django/db/backends/utils.py", line 84, in _execute
> return self.cursor.execute(sql, params)
>   File "…/Vcs/django/django/db/backends/sqlite3/base.py", line 391, in
> execute
> return Database.Cursor.execute(self, query, params)
> sqlite3.OperationalError: database is locked
>
> The above exception was the direct cause of the following exception:
>
> Traceback (most recent call last):
>   File "…/Vcs/django/django/test/testcases.py", line 1137, in setUpClass
> cls.setUpTestData()
>   File "…/Vcs/django/tests/admin_views/test_multidb.py", line 40, in
> setUpTestData
> username='admin', password='something', email='t...@test.org',
>   File "…/Vcs/django/django/contrib/auth/models.py", line 158, in
> create_superuser
> return self._create_user(username, email, password, **extra_fields)
>   File "…/Vcs/django/django/contrib/auth/models.py", line 141, in
> _create_user
> user.save(using=self._db)
>   File "…/Vcs/django/django/contrib/auth/base_user.py", line 66, in save
> super().save(*args, **kwargs)
>   File "…/Vcs/django/django/db/models/base.py", line 741, in save
> force_update=force_update, update_fields=update_fields)
>   File "…/Vcs/django/django/db/models/base.py", line 779, in save_base
> force_update, using, update_fields,
>   File "…/Vcs/django/django/db/models/base.py", line 870, in _save_table
> result = self._do_insert(cls._base_manager, using, fields, update_pk,
> raw)
>   File "…/Vcs/django/django/db/models/base.py", line 908, in _do_insert
> using=using, raw=raw)
>   File "…/Vcs/django/django/db/models/manager.py", line 82, in
> manager_method
> return getattr(self.get_queryset(), name)(*args, **kwargs)
>   File "…/Vcs/django/django/db/models/query.py", line 1175, in _insert
> return 

Re: [Django] #29097: Migrations using MySQL fail for constraints using composite indexes

[Django]

#29097: Migrations using MySQL fail for constraints using composite indexes
-+-
 Reporter:  geertjanvdk  |Owner:  (none)
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:  introspection mysql  | Triage Stage:  Accepted
  migration index constraint |
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Simon Charette):

 * component:  Database layer (models, ORM) => Migrations


-- 
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/069.ae89d6827da357663d29d2165406a2a3%40djangoproject.com.

Re: [Django] #29955: Support dwithin lookup on F expressions for distance stored in model

[Django]

#29955: Support dwithin lookup on F expressions for distance stored in model
-+-
 Reporter:  Peter Bex|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  GIS  |  Version:  2.1
 Severity:  Normal   |   Resolution:
 Keywords:  distance, query  | Triage Stage:  Accepted
  builder, F expressions |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Simon Charette):

 I suspect this has been fixed by 8a281aa7fe76a9da2284f943964a9413697cff1f
 (#30687) but I cannot confirm it because the provided test case doesn't
 work out of the fox (`allowed_distance` is referring to a non existing
 field).

 Peter, please confirm whether or not the aforementioned commit resolves
 your issue or provide a working test case or at least a full traceback.

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

Re: [Django] #30413: admin_views.test_multidb fails with persistent test SQLite database.

[Django]

#30413: admin_views.test_multidb fails with persistent test SQLite database.
-+-
 Reporter:  Daniel Hahler|Owner:  Ngalim
 |  Siregar
 Type:  Bug  |   Status:  assigned
Component:  Testing framework|  Version:  master
 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
-+-
Changes (by Ngalim Siregar):

 * has_patch:  0 => 1


Old description:

> I've tried using persistent SQLite databases for the tests (to make use
> of
> `--keepdb`), but at least some test fails with:
>
> > sqlite3.OperationalError: database is locked
>
> This is not an issue when only using `TEST["NAME"]` with "default" (which
> is good enough in terms of performance).
>
> {{{
> diff --git i/tests/test_sqlite.py w/tests/test_sqlite.py
> index f1b65f7d01..9ce4e32e14 100644
> --- i/tests/test_sqlite.py
> +++ w/tests/test_sqlite.py
> @@ -15,9 +15,15 @@
>  DATABASES = {
>  'default': {
>  'ENGINE': 'django.db.backends.sqlite3',
> +'TEST': {
> +'NAME': 'test_default.sqlite3'
> +},
>  },
>  'other': {
>  'ENGINE': 'django.db.backends.sqlite3',
> +'TEST': {
> +'NAME': 'test_other.sqlite3'
> +},
>  }
>  }
> }}}
>
> {{{
> % tests/runtests.py admin_views.test_multidb -v 3 --keepdb --parallel 1
> …
> Operations to perform:
>   Synchronize unmigrated apps: admin_views, auth, contenttypes, messages,
> sessions, staticfiles
>   Apply all migrations: admin, sites
> Running pre-migrate handlers for application contenttypes
> Running pre-migrate handlers for application auth
> Running pre-migrate handlers for application sites
> Running pre-migrate handlers for application sessions
> Running pre-migrate handlers for application admin
> Running pre-migrate handlers for application admin_views
> Synchronizing apps without migrations:
>   Creating tables...
> Running deferred SQL...
> Running migrations:
>   No migrations to apply.
> Running post-migrate handlers for application contenttypes
> Running post-migrate handlers for application auth
> Running post-migrate handlers for application sites
> Running post-migrate handlers for application sessions
> Running post-migrate handlers for application admin
> Running post-migrate handlers for application admin_views
> System check identified no issues (0 silenced).
> ERROR
>
> ==
> ERROR: setUpClass (admin_views.test_multidb.MultiDatabaseTests)
> --
> Traceback (most recent call last):
>   File "…/Vcs/django/django/db/backends/utils.py", line 84, in _execute
> return self.cursor.execute(sql, params)
>   File "…/Vcs/django/django/db/backends/sqlite3/base.py", line 391, in
> execute
> return Database.Cursor.execute(self, query, params)
> sqlite3.OperationalError: database is locked
>
> The above exception was the direct cause of the following exception:
>
> Traceback (most recent call last):
>   File "…/Vcs/django/django/test/testcases.py", line 1137, in setUpClass
> cls.setUpTestData()
>   File "…/Vcs/django/tests/admin_views/test_multidb.py", line 40, in
> setUpTestData
> username='admin', password='something', email='t...@test.org',
>   File "…/Vcs/django/django/contrib/auth/models.py", line 158, in
> create_superuser
> return self._create_user(username, email, password, **extra_fields)
>   File "…/Vcs/django/django/contrib/auth/models.py", line 141, in
> _create_user
> user.save(using=self._db)
>   File "…/Vcs/django/django/contrib/auth/base_user.py", line 66, in save
> super().save(*args, **kwargs)
>   File "…/Vcs/django/django/db/models/base.py", line 741, in save
> force_update=force_update, update_fields=update_fields)
>   File "…/Vcs/django/django/db/models/base.py", line 779, in save_base
> force_update, using, update_fields,
>   File "…/Vcs/django/django/db/models/base.py", line 870, in _save_table
> result = self._do_insert(cls._base_manager, using, fields, update_pk,
> raw)
>   File "…/Vcs/django/django/db/models/base.py", line 908, in _do_insert
> using=using, raw=raw)
>   File "…/Vcs/django/django/db/models/manager.py", line 82, in
> manager_method
> return getattr(self.get_queryset(), name)(*args, **kwargs)
>   File "…/Vcs/django/django/db/models/query.py", line 1175, in _insert
> return query.get_compiler(using=using).execute_sql(return_id)
>   File 

Re: [Django] #30691: Change uuid field to FK does not create dependency

[Django]

#30691: Change uuid field to FK does not create dependency
+
 Reporter:  Dart|Owner:  Dart
 Type:  Bug |   Status:  assigned
Component:  Migrations  |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  UUID, FK| Triage Stage:  Accepted
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+

Comment (by Simon Charette):

 Hello Dart,

 Are you still planing to work on this? Do you need any assistance
 submitting 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.7b0632252bf10a2298b601b6eb5d75c4%40djangoproject.com.

Re: [Django] #29545: Nested OuterRef not looking on the right model for the field.

[Django]

#29545: Nested OuterRef not looking on the right model for the field.
-+-
 Reporter:  Aaron Lisman |Owner:  Simon
 |  Charette
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  outerref, subquery   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Simon Charette):

 * has_patch:  0 => 1


Comment:

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

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

Re: [Django] #30694: Document FileResponse does not seek its file source

[Django]

#30694: Document FileResponse does not seek its file source
---+
 Reporter:  Claude Paroz   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  2.2
 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
---+
Changes (by Claude Paroz):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/11676 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.82a9467c78e648e02e664b14269809ad%40djangoproject.com.

Re: [Django] #30701: Allowing patch_vary_headers() caching utility to handle '*' value.

[Django]

#30701: Allowing patch_vary_headers() caching utility to handle '*' value.
-+-
 Reporter:  Alexander-TX |Owner:  Adnan
 Type:   |  Umer
  Cleanup/optimization   |   Status:  closed
Component:  Core (Cache system)  |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Mariusz Felisiak ):

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


Comment:

 In [changeset:"6805c0f99f4790f28a97d597934d0877ba81dba9" 6805c0f9]:
 {{{
 #!CommitTicketReference repository=""
 revision="6805c0f99f4790f28a97d597934d0877ba81dba9"
 Fixed #30701 -- Updated patch_vary_headers() to handle an asterisk
 according to RFC 7231.
 }}}

-- 
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/070.e20d0348f856111e5ffba95516e95af2%40djangoproject.com.

Re: [Django] #30701: Allowing patch_vary_headers() caching utility to handle '*' value.

[Django]

#30701: Allowing patch_vary_headers() caching utility to handle '*' value.
-+-
 Reporter:  Alexander-TX |Owner:  Adnan
 Type:   |  Umer
  Cleanup/optimization   |   Status:  assigned
Component:  Core (Cache system)  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Carlton Gibson):

 * stage:  Accepted => Ready for checkin


Comment:

 PR Looks good.

-- 
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/070.9441e0b93d92ff72243722ea440ed30b%40djangoproject.com.

Re: [Django] #30413: admin_views.test_multidb fails with persistent test SQLite database.

[Django]

#30413: admin_views.test_multidb fails with persistent test SQLite database.
-+-
 Reporter:  Daniel Hahler|Owner:  Ngalim
 |  Siregar
 Type:  Bug  |   Status:  assigned
Component:  Testing framework|  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 Ngalim Siregar):

 * owner:  nobody => Ngalim Siregar
 * status:  new => assigned


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

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

Re: [Django] #30701: Allowing patch_vary_headers() caching utility to handle '*' value.

[Django]

#30701: Allowing patch_vary_headers() caching utility to handle '*' value.
-+-
 Reporter:  Alexander-TX |Owner:  Adnan
 Type:   |  Umer
  Cleanup/optimization   |   Status:  assigned
Component:  Core (Cache system)  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by felixxm):

 * has_patch:  0 => 1
 * type:  New feature => Cleanup/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/070.2d8509bb25df232d2e62f3d554c5620c%40djangoproject.com.

Re: [Django] #28344: Add for_update parameter to Model.refresh_from_db()

[Django]

#28344: Add for_update parameter to Model.refresh_from_db()
-+-
 Reporter:  Patryk Zawadzki  |Owner:  (none)
 Type:  New feature  |   Status:  new
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 Andrey Maslov):

 * cc: Andrey Maslov (added)


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

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

Re: [Django] #30701: Allowing patch_vary_headers() caching utility to handle '*' value.

[Django]

#30701: Allowing patch_vary_headers() caching utility to handle '*' value.
-+-
 Reporter:  Alexander-TX |Owner:  Adnan
 |  Umer
 Type:  New feature  |   Status:  assigned
Component:  Core (Cache system)  |  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 Ngalim Siregar):

 * owner:  Ngalim Siregar => Adnan Umer


-- 
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/070.0b9a6f8f22947966dd7264db17d4cf4e%40djangoproject.com.

Re: [Django] #30701: Allowing patch_vary_headers() caching utility to handle '*' value.

[Django]

#30701: Allowing patch_vary_headers() caching utility to handle '*' value.
-+-
 Reporter:  Alexander-TX |Owner:  Ngalim
 |  Siregar
 Type:  New feature  |   Status:  assigned
Component:  Core (Cache system)  |  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 Ngalim Siregar):

 * owner:  Adnan Umer => Ngalim Siregar


-- 
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/070.31bad7e593f9e7bb1576a75a4b1e2c23%40djangoproject.com.

Re: [Django] #30710: impossible without workarounds to see which fields changed when subscribing to signals from generic views

[Django]

#30710: impossible without workarounds to see which fields changed when 
subscribing
to signals from generic views
---+--
 Reporter:  MaxR   |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Uncategorized  |  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
---+--
Changes (by Carlton Gibson):

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


Comment:

 This is the expected behaviour
 
([https://docs.djangoproject.com/en/2.2/ref/signals/#django.db.models.signals.post_save
 as documented]).

 As per [https://docs.djangoproject.com/en/2.2/ref/models/instances
 /#specifying-which-fields-to-save Specifying which fields to save] the
 saved fields are only limited if you pass `update_fields`, otherwise it's
 all, so you don't need it in `post_save`.

 If you want to pass `update_fields`, override your form's `save()`
 accordingly.

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

Re: [Django] #30705: Django template permissions not working when used inside the template of an inclusion tag

[Django]

#30705: Django template permissions not working when used inside the template 
of an
inclusion tag
-+-
 Reporter:  erev0s   |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Template system  |  Version:  2.2
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:  permissions, | Triage Stage:
  inclusion tag  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Carlton Gibson):

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


Comment:

 Hi. I suspect there's not a bug here but, as it stands there not enough
 information to know...

 Could you upload a minimal project that recreates your issue so we can
 have a look? Thanks.

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

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

Re: [Django] #27676: MariaDB 10.2 supports defaults for text columns

[Django]

#27676: MariaDB 10.2 supports defaults for text columns
-+-
 Reporter:  Adam (Chainz)|Owner:  Adam
  Johnson|  (Chainz) Johnson
 Type:  New feature  |   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 Mariusz Felisiak ):

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


Comment:

 In [changeset:"7da6a28a447dc0db2a2c6ef31894094eb968f408" 7da6a28a]:
 {{{
 #!CommitTicketReference repository=""
 revision="7da6a28a447dc0db2a2c6ef31894094eb968f408"
 Fixed #27676 -- Allowed BLOB/TEXT defaults on MariaDB 10.2.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/068.3edd1fba0aaa37df3a88a17ec2e499b1%40djangoproject.com.

Re: [Django] #30687: GIS distance lookups fail within subqueries using OuterRef

[Django]

#30687: GIS distance lookups fail within subqueries using OuterRef
-+-
 Reporter:  Andrew Brown |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak ):

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


Comment:

 In [changeset:"8a281aa7fe76a9da2284f943964a9413697cff1f" 8a281aa7]:
 {{{
 #!CommitTicketReference repository=""
 revision="8a281aa7fe76a9da2284f943964a9413697cff1f"
 Fixed #30687 -- Fixed using of OuterRef() expressions in distance lookups.
 }}}

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