Re: [Django] #29406: Add Referrer-Policy header support

[Django]

#29406: Add Referrer-Policy header support
---+-
 Reporter:  James Bennett  |Owner:  James Bennett
 Type:  New feature|   Status:  assigned
Component:  Utilities  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Someday/Maybe
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+-
Changes (by James Bennett):

 * stage:  Accepted => Someday/Maybe


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

Re: [Django] #29406: Add Referrer-Policy header support

[Django]

#29406: Add Referrer-Policy header support
---+-
 Reporter:  James Bennett  |Owner:  James Bennett
 Type:  New feature|   Status:  assigned
Component:  Utilities  |  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 James Bennett):

 I'm going to leave this on hold for now. I'm currently supporting the
 feature via a third-party app (django-referrer-policy), and I want to work
 out the issues with browser support there, rather than burden Django
 itself with them. Once that's figured out, I'll contribute the code back
 to Django.

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

Re: [Django] #28073: RemoveField.state_forwards() crashes with AttributeError: 'NoneType' object has no attribute 'is_relation'

[Django]

#28073: RemoveField.state_forwards() crashes with AttributeError: 'NoneType' 
object
has no attribute 'is_relation'
-+
 Reporter:  Logan Gunthorpe  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by yuanxu):

 I had the same issue. In my case, I agree with  testvinder.  In my case,
 I've delete some fields in db, and have RemoveField in migrations. In
 1.10.7, It works fun and crash in 2.0.7.

 I just modify the fields.py in line 145 with:

 {{{
  delay = old_field is None or  not old_field.is_relation
 }}}

 It works! but I don't know if is there are other issues.

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

Re: [Django] #29451: Add compatibility with MySQL 8

[Django]

#29451: Add compatibility with MySQL 8
-+-
 Reporter:  Tim Graham   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
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
-+-

Comment (by Tom Forbes):

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

 I get two other failures locally, but I assume they are to do with my
 environment:


 {{{
 ==
 FAIL: test_raster_transform
 (gis_tests.gdal_tests.test_raster.GDALRasterTests)
 --
 Traceback (most recent call last):
   File
 "/Users/tom/PycharmProjects/django/tests/gis_tests/gdal_tests/test_raster.py",
 line 517, in test_raster_transform
 self.assertAlmostEqual(target.origin[0], 9124842.791079799)
 AssertionError: 9124842.791069634 != 9124842.791079799 within 7 places

 --

 ==
 FAIL: test_transform_3d (gis_tests.geos_tests.test_geos.GEOSTest)
 --
 Traceback (most recent call last):
   File
 "/Users/tom/PycharmProjects/django/tests/gis_tests/geos_tests/test_geos.py",
 line 1121, in test_transform_3d
 self.assertEqual(p3d.z, 100)
 AssertionError: 100.1595821232 != 100

 --
 }}}

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

Re: [Django] #29451: Add compatibility with MySQL 8

[Django]

#29451: Add compatibility with MySQL 8
-+-
 Reporter:  Tim Graham   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
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
-+-

Comment (by Tom Forbes):

 Regarding the `test_isvalid_lookup` failure, thankfully it seems that it's
 not really a failure. A comment in the test says:


 {{{
 # Kansas has adjacent vertices with distance 6.99244813842e-12
 # which is smaller than the default Oracle tolerance.
 # It's invalid on MySQL too.
 }}}

 This doesn't seem to be the case anymore. Skipping that branch, where the
 failure originates, makes the test pass just fine. I'll prepare a PR 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/067.50bb2819770e1c24a5b489ca53772973%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29157: Allow querying for distinct values in JSONField lists

[Django]

#29157: Allow querying for distinct values in JSONField lists
---+
 Reporter:  Hrishikesh Barman  |Owner:  (none)
 Type:  New feature|   Status:  new
Component:  contrib.postgres   |  Version:  2.0
 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 Joey Wilhelm):

 * cc: Joey Wilhelm (added)


Comment:

 I have a similar use case. Using the following model...

 {{{#!python
 class Request(models.Model):
 request_data = JSONField()
 state = models.CharField(max_length=255)
 }}}

 And JSON data
 {{{#!json
 {"target": {"pk": 1}}
 }}}

 I'm able to issue a SQL query like this:

 {{{#!sql
 SELECT DISTINCT(request_data -> 'target' -> 'pk') FROM myapp_request WHERE
 state = 'in_progress';
 }}}

 I would expect the equivalent ORM code to look like:

 {{{#!python
 
Request.objects.filter(state=Request.STATE_IN_PROGRESS).values('request_data__target__pk').distinct()
 }}}
 OR
 {{{#!python
 
Request.objects.filter(state=Request.STATE_IN_PROGRESS).annotate(target=F('request_data__target__pk')).values('target').distinct()
 }}}
 But both produce this error:
 {{{#!python
 django.core.exceptions.FieldError: Cannot resolve keyword 'target' into
 field. Join on 'request_data' not permitted.
 }}}

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

Re: [Django] #28935: Template error raised in an {% extends %} child template shows incorrect source location on debug page

[Django]

#28935: Template error raised in an {% extends %} child template shows incorrect
source location on debug page
-+--
 Reporter:  Matt Westcott|Owner:  Ankur Jain
 Type:  Bug  |   Status:  assigned
Component:  Template system  |  Version:  2.0
 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 Ankur Jain):

 * owner:  (none) => Ankur Jain
 * 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 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.669b283f9e62fb8ee304e71404a4ec0c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29546: deprecate timezone.FixedOffset in favor of datetime.timezone

[Django]

#29546: deprecate timezone.FixedOffset in favor of datetime.timezone
-+-
 Reporter:  Sergey Fedoseev  |Owner:  Sergey
 Type:   |  Fedoseev
  Cleanup/optimization   |   Status:  assigned
Component:  Utilities|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Sergey Fedoseev):

 * status:  new => assigned
 * owner:  nobody => Sergey Fedoseev


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

[Django] #29546: deprecate timezone.FixedOffset in favor of datetime.timezone

[Django]

#29546: deprecate timezone.FixedOffset in favor of datetime.timezone
+
   Reporter:  Sergey Fedoseev   |  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  Utilities |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 |
+
 We have `FixedOffset` class each instance of which represents a timezone
 defined by a fixed offset from UTC, in Python 3.2 was added
 `datetime.timezone` class needed for the same purpose, so now we can get
 rid of our implementation.
 The possible pitfall is that `FixedOffset.dst()` returns `timedelta(0)`,
 but `datetime.timezone.dst()` returns `None`.

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

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

[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:  pwfff  |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Database   |Version:  2.0
  layer (models, ORM)|
   Severity:  Normal |   Keywords:  outerref, subquery
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 I ran into this and made a test case for it. It seems similar to the test
 case above it. I'm not sure what's different about it and causing it to
 fail.

 Let me know if the query is just build wrong.

 {{{
 diff --git a/tests/expressions/models.py b/tests/expressions/models.py
 index 42e4a37bb0..164bda3b3d 100644
 --- a/tests/expressions/models.py
 +++ b/tests/expressions/models.py
 @@ -83,6 +83,28 @@ class SimulationRun(models.Model):
  return "%s (%s to %s)" % (self.midpoint, self.start, self.end)


 +class Customer(models.Model):
 +name = models.TextField()
 +
 +
 +class Item(models.Model):
 +pass
 +
 +
 +class Invoice(models.Model):
 +INVOICE = 'invoice'
 +EXPENSE = 'expense'
 +
 +KIND_CHOICES = (
 +(INVOICE, 'Invoice'),
 +(EXPENSE, 'Expense'),
 +)
 +
 +kind = models.CharField(choices=KIND_CHOICES, max_length=255,
 default=None)
 +owner = models.ForeignKey(Customer, models.CASCADE)
 +items = models.ManyToManyField(Item, related_name='invoices')
 +
 +
  class UUIDPK(models.Model):
  id = models.UUIDField(primary_key=True, default=uuid.uuid4)

 diff --git a/tests/expressions/tests.py b/tests/expressions/tests.py
 index d1e622a2d4..2c50744fc8 100644
 --- a/tests/expressions/tests.py
 +++ b/tests/expressions/tests.py
 @@ -24,7 +24,7 @@ from django.test.utils import Approximate

  from .models import (
  UUID, UUIDPK, Company, Employee, Experiment, Number, Result,
 SimulationRun,
 -Time,
 +Time, Customer, Item, Invoice
  )


 @@ -536,6 +536,55 @@ class BasicExpressionsTests(TestCase):
  # This is a contrived example. It exercises the double OuterRef
 form.
  self.assertCountEqual(outer, [first, second, third])

 +def test_nested_subquery_outer_ref_3(self):
 +customer = Customer.objects.create(name='Test Customer')
 +other_customer = Customer.objects.create(name='Ohter Customer')
 +
 +unexpensed_invoice = Invoice.objects.create(kind=Invoice.INVOICE,
 owner=customer)
 +unexpensed_item_1 = Item.objects.create()
 +unexpensed_invoice.items.add(unexpensed_item_1)
 +
 +partially_expensed_invoice =
 Invoice.objects.create(kind=Invoice.INVOICE, owner=customer)
 +expense_1 = Invoice.objects.create(kind=Invoice.EXPENSE,
 owner=customer)
 +expensed_item_1 = Item.objects.create()
 +unexpensed_item_2 = Item.objects.create()
 +partially_expensed_invoice.items.add(expensed_item_1,
 unexpensed_item_2)
 +expense_1.items.add(expensed_item_1)
 +
 +expensed_invoice = Invoice.objects.create(kind=Invoice.INVOICE,
 owner=customer)
 +Invoice.objects.create(kind=Invoice.EXPENSE, owner=customer)
 +expensed_item_2 = Item.objects.create()
 +expensed_invoice.items.add(expensed_item_2)
 +expense_1.items.add(expensed_item_2)
 +
 +other_invoice = Invoice.objects.create(kind=Invoice.INVOICE,
 owner=other_customer)
 +other_invoice.items.add(unexpensed_item_1)
 +other_expense = Invoice.objects.create(kind=Invoice.EXPENSE,
 owner=other_customer)
 +other_expense.items.add(unexpensed_item_1)
 +
 +inner = Invoice.objects.filter(
 +kind=Invoice.EXPENSE,
 +owner=OuterRef(OuterRef('owner')),
 +items=OuterRef('id'),
 +)
 +middle = Item.objects.filter(
 +invoices=OuterRef('id'),
 +).annotate(
 +expensed=Exists(inner),
 +).filter(
 +expensed=False,
 +)
 +outer = Invoice.objects.filter(
 +kind=Invoice.INVOICE,
 +owner=customer,
 +).annotate(
 +unexpensed=Exists(middle),
 +)
 +
 +self.assertTrue(outer.get(pk=unexpensed_invoice.pk).unexpensed)
 +
 self.assertTrue(outer.get(pk=partially_expensed_invoice.pk).unexpensed)
 +self.assertFalse(outer.get(pk=expensed_invoice.pk).unexpensed)
 +
  def test_nested_subquery_outer_ref_with_autofield(self):
  first = Time.objects.create(time='09:00')
  second = Time.objects.create(time='17:00')
 }}}

 {{{
 django.core.exceptions.FieldError: Cannot resolve keyword 'owner' into
 field. Choices are: 

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:  pwfff|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  2.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  outerref, subquery   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Description changed by pwfff:

Old description:

> I ran into this and made a test case for it. It seems similar to the test
> case above it. I'm not sure what's different about it and causing it to
> fail.
>
> Let me know if the query is just build wrong.
>
> {{{
> diff --git a/tests/expressions/models.py b/tests/expressions/models.py
> index 42e4a37bb0..164bda3b3d 100644
> --- a/tests/expressions/models.py
> +++ b/tests/expressions/models.py
> @@ -83,6 +83,28 @@ class SimulationRun(models.Model):
>  return "%s (%s to %s)" % (self.midpoint, self.start, self.end)
>

> +class Customer(models.Model):
> +name = models.TextField()
> +
> +
> +class Item(models.Model):
> +pass
> +
> +
> +class Invoice(models.Model):
> +INVOICE = 'invoice'
> +EXPENSE = 'expense'
> +
> +KIND_CHOICES = (
> +(INVOICE, 'Invoice'),
> +(EXPENSE, 'Expense'),
> +)
> +
> +kind = models.CharField(choices=KIND_CHOICES, max_length=255,
> default=None)
> +owner = models.ForeignKey(Customer, models.CASCADE)
> +items = models.ManyToManyField(Item, related_name='invoices')
> +
> +
>  class UUIDPK(models.Model):
>  id = models.UUIDField(primary_key=True, default=uuid.uuid4)
>
> diff --git a/tests/expressions/tests.py b/tests/expressions/tests.py
> index d1e622a2d4..2c50744fc8 100644
> --- a/tests/expressions/tests.py
> +++ b/tests/expressions/tests.py
> @@ -24,7 +24,7 @@ from django.test.utils import Approximate
>
>  from .models import (
>  UUID, UUIDPK, Company, Employee, Experiment, Number, Result,
> SimulationRun,
> -Time,
> +Time, Customer, Item, Invoice
>  )
>

> @@ -536,6 +536,55 @@ class BasicExpressionsTests(TestCase):
>  # This is a contrived example. It exercises the double OuterRef
> form.
>  self.assertCountEqual(outer, [first, second, third])
>
> +def test_nested_subquery_outer_ref_3(self):
> +customer = Customer.objects.create(name='Test Customer')
> +other_customer = Customer.objects.create(name='Ohter Customer')
> +
> +unexpensed_invoice =
> Invoice.objects.create(kind=Invoice.INVOICE, owner=customer)
> +unexpensed_item_1 = Item.objects.create()
> +unexpensed_invoice.items.add(unexpensed_item_1)
> +
> +partially_expensed_invoice =
> Invoice.objects.create(kind=Invoice.INVOICE, owner=customer)
> +expense_1 = Invoice.objects.create(kind=Invoice.EXPENSE,
> owner=customer)
> +expensed_item_1 = Item.objects.create()
> +unexpensed_item_2 = Item.objects.create()
> +partially_expensed_invoice.items.add(expensed_item_1,
> unexpensed_item_2)
> +expense_1.items.add(expensed_item_1)
> +
> +expensed_invoice = Invoice.objects.create(kind=Invoice.INVOICE,
> owner=customer)
> +Invoice.objects.create(kind=Invoice.EXPENSE, owner=customer)
> +expensed_item_2 = Item.objects.create()
> +expensed_invoice.items.add(expensed_item_2)
> +expense_1.items.add(expensed_item_2)
> +
> +other_invoice = Invoice.objects.create(kind=Invoice.INVOICE,
> owner=other_customer)
> +other_invoice.items.add(unexpensed_item_1)
> +other_expense = Invoice.objects.create(kind=Invoice.EXPENSE,
> owner=other_customer)
> +other_expense.items.add(unexpensed_item_1)
> +
> +inner = Invoice.objects.filter(
> +kind=Invoice.EXPENSE,
> +owner=OuterRef(OuterRef('owner')),
> +items=OuterRef('id'),
> +)
> +middle = Item.objects.filter(
> +invoices=OuterRef('id'),
> +).annotate(
> +expensed=Exists(inner),
> +).filter(
> +expensed=False,
> +)
> +outer = Invoice.objects.filter(
> +kind=Invoice.INVOICE,
> +owner=customer,
> +).annotate(
> +unexpensed=Exists(middle),
> +)
> +
> +self.assertTrue(outer.get(pk=unexpensed_invoice.pk).unexpensed)
> +
> self.assertTrue(outer.get(pk=partially_expensed_invoice.pk).unexpensed)
> +self.assertFalse(outer.get(pk=expensed_invoice.pk).unexpensed)
> +
>  def 

Re: [Django] #29544: Django 2.0.7 broke regex lookup on MariaDB

[Django]

#29544: Django 2.0.7 broke regex lookup on MariaDB
-+-
 Reporter:  Michal Čihař |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  2.0
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"1645471348ac6012ad9444742f6e572ecf7c993b" 16454713]:
 {{{
 #!CommitTicketReference repository=""
 revision="1645471348ac6012ad9444742f6e572ecf7c993b"
 [2.0.x] Fixed #29544 -- Fixed regex lookup on MariaDB.

 Regression in 42490768441701bc02255b22df8e6894cbe487c7.
 Backport of 39e287d8bff50e9f91f3f4471088c1946aa6a76c 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/063.36b7aced461ed27ac7500587ff230192%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29544: Django 2.0.7 broke regex lookup on MariaDB

[Django]

#29544: Django 2.0.7 broke regex lookup on MariaDB
-+-
 Reporter:  Michal Čihař |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  2.0
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"c1ac9c5ea38e26f2b017cc618918a9283fd55f56" c1ac9c5e]:
 {{{
 #!CommitTicketReference repository=""
 revision="c1ac9c5ea38e26f2b017cc618918a9283fd55f56"
 [2.1.x] Fixed #29544 -- Fixed regex lookup on MariaDB.

 Regression in 42490768441701bc02255b22df8e6894cbe487c7.
 Backport of 39e287d8bff50e9f91f3f4471088c1946aa6a76c 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/063.ccb919436cabc7acf6b4ef355041daa4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29544: Django 2.0.7 broke regex lookup on MariaDB

[Django]

#29544: Django 2.0.7 broke regex lookup on MariaDB
-+-
 Reporter:  Michal Čihař |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  2.0
  (models, ORM)  |
 Severity:  Release blocker  |   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 Tim Graham ):

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


Comment:

 In [changeset:"39e287d8bff50e9f91f3f4471088c1946aa6a76c" 39e287d8]:
 {{{
 #!CommitTicketReference repository=""
 revision="39e287d8bff50e9f91f3f4471088c1946aa6a76c"
 Fixed #29544 -- Fixed regex lookup on MariaDB.

 Regression in 42490768441701bc02255b22df8e6894cbe487c7.
 }}}

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

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

Re: [Django] #29544: Django 2.0.7 broke regex lookup on MariaDB

[Django]

#29544: Django 2.0.7 broke regex lookup on MariaDB
-+-
 Reporter:  Michal Čihař |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  2.0
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Description changed by Tim Graham:

Old description:

> Since Django 2.0.7 it fails to do regexp lookups on MariaDB. The problem
> is in code introduced for https://code.djangoproject.com/ticket/29451 -
> it assumes that MariaDB 10.3 has REGEXP_LIKE what is not true.
>
> The exception is:
>

> {{{
> Traceback (most recent call last):
>   File "/home/travis/virtualenv/python3.6.3/lib/python3.6/site-
> packages/django/db/backends/utils.py", line 85, in _execute
> return self.cursor.execute(sql, params)
>   File "/home/travis/virtualenv/python3.6.3/lib/python3.6/site-
> packages/django/db/backends/mysql/base.py", line 71, in execute
> return self.cursor.execute(query, args)
>   File "/home/travis/virtualenv/python3.6.3/lib/python3.6/site-
> packages/MySQLdb/cursors.py", line 250, in execute
> self.errorhandler(self, exc, value)
>   File "/home/travis/virtualenv/python3.6.3/lib/python3.6/site-
> packages/MySQLdb/connections.py", line 50, in defaulterrorhandler
> raise errorvalue
>   File "/home/travis/virtualenv/python3.6.3/lib/python3.6/site-
> packages/MySQLdb/cursors.py", line 247, in execute
> res = self._query(query)
>   File "/home/travis/virtualenv/python3.6.3/lib/python3.6/site-
> packages/MySQLdb/cursors.py", line 412, in _query
> rowcount = self._do_query(q)
>   File "/home/travis/virtualenv/python3.6.3/lib/python3.6/site-
> packages/MySQLdb/cursors.py", line 375, in _do_query
> db.query(q)
>   File "/home/travis/virtualenv/python3.6.3/lib/python3.6/site-
> packages/MySQLdb/connections.py", line 276, in query
> _mysql.connection.query(self, query)
> _mysql_exceptions.OperationalError: (1305, 'FUNCTION
> test_weblate.REGEXP_LIKE does not exist')
> }}}

New description:

 Since Django 2.0.7 it fails to do regex lookups on MariaDB. The problem is
 in code introduced for #29451 - it assumes that MariaDB 10.3 has
 REGEXP_LIKE what is not true.

 The exception is:

 {{{
 Traceback (most recent call last):
   File "/home/travis/virtualenv/python3.6.3/lib/python3.6/site-
 packages/django/db/backends/utils.py", line 85, in _execute
 return self.cursor.execute(sql, params)
   File "/home/travis/virtualenv/python3.6.3/lib/python3.6/site-
 packages/django/db/backends/mysql/base.py", line 71, in execute
 return self.cursor.execute(query, args)
   File "/home/travis/virtualenv/python3.6.3/lib/python3.6/site-
 packages/MySQLdb/cursors.py", line 250, in execute
 self.errorhandler(self, exc, value)
   File "/home/travis/virtualenv/python3.6.3/lib/python3.6/site-
 packages/MySQLdb/connections.py", line 50, in defaulterrorhandler
 raise errorvalue
   File "/home/travis/virtualenv/python3.6.3/lib/python3.6/site-
 packages/MySQLdb/cursors.py", line 247, in execute
 res = self._query(query)
   File "/home/travis/virtualenv/python3.6.3/lib/python3.6/site-
 packages/MySQLdb/cursors.py", line 412, in _query
 rowcount = self._do_query(q)
   File "/home/travis/virtualenv/python3.6.3/lib/python3.6/site-
 packages/MySQLdb/cursors.py", line 375, in _do_query
 db.query(q)
   File "/home/travis/virtualenv/python3.6.3/lib/python3.6/site-
 packages/MySQLdb/connections.py", line 276, in query
 _mysql.connection.query(self, query)
 _mysql_exceptions.OperationalError: (1305, 'FUNCTION
 test_weblate.REGEXP_LIKE does not exist')
 }}}

--

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

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

Re: [Django] #29544: Django 2.0.7 broke regex lookup on MariaDB (was: Add a MariaDB database backend)

[Django]

#29544: Django 2.0.7 broke regex lookup on MariaDB
-+-
 Reporter:  Michal Čihař |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  2.0
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * has_patch:  0 => 1
 * version:  master => 2.0
 * type:  New feature => Bug
 * stage:  Accepted => Ready for checkin


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

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

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:  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
-+-

Comment (by Tim Graham ):

 In [changeset:"2ce830e683ad2ce60cfdc0d77866fc2e55a48b9f" 2ce830e]:
 {{{
 #!CommitTicketReference repository=""
 revision="2ce830e683ad2ce60cfdc0d77866fc2e55a48b9f"
 [2.0.x] Refs #26608 -- Removed incorrect sentence in
 Expression.contains_over_clause docs.

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

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:  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
-+-

Comment (by Tim Graham ):

 In [changeset:"b505cef63db39abe989ac05c3cf20544b61d8bf0" b505cef]:
 {{{
 #!CommitTicketReference repository=""
 revision="b505cef63db39abe989ac05c3cf20544b61d8bf0"
 [2.1.x] Refs #26608 -- Removed incorrect sentence in
 Expression.contains_over_clause docs.

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

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:  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
-+-

Comment (by Tim Graham ):

 In [changeset:"f1fc7d6b78186171923a9351eb7af3b5b7565156" f1fc7d6]:
 {{{
 #!CommitTicketReference repository=""
 revision="f1fc7d6b78186171923a9351eb7af3b5b7565156"
 Refs #26608 -- Removed unneeded name attribute in window functions.
 }}}

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

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:  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
-+-

Comment (by Tim Graham ):

 In [changeset:"ab251fdad251cfb1e9fb61c42b5bfed9d0afe393" ab251fd]:
 {{{
 #!CommitTicketReference repository=""
 revision="ab251fdad251cfb1e9fb61c42b5bfed9d0afe393"
 Refs #26608 -- Removed incorrect sentence in
 Expression.contains_over_clause docs.
 }}}

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

Re: [Django] #28643: Complete the ORM Function Library

[Django]

#28643: Complete the ORM Function Library
-+-
 Reporter:  Matthew Pava |Owner:  JunyiJ
 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
-+-

Comment (by Tim Graham ):

 In [changeset:"a0b19a0f5b1731cf575546175034da53f5af5367" a0b19a0]:
 {{{
 #!CommitTicketReference repository=""
 revision="a0b19a0f5b1731cf575546175034da53f5af5367"
 Refs #28643 -- Added math database functions.

 Thanks Nick Pope for much review.
 }}}

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

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

Re: [Django] #29544: Add a MariaDB database backend

[Django]

#29544: Add a MariaDB database backend
-+-
 Reporter:  Michal Čihař |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Release blocker  |   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 Claude Paroz):

 Absolutely, but patches are waiting for a CI instance with MariaDB. Even
 if we know there are some failures with MariaDB, at least this would
 prevent massive breakage like this one (I don't blame you or anyone else,
 to be clear).

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

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

Re: [Django] #29544: Add a MariaDB database backend

[Django]

#29544: Add a MariaDB database backend
-+-
 Reporter:  Michal Čihař |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Release blocker  |   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 Tom Forbes):

 It would be possible to fix the patch I made by detecting MariaDB (or more
 specifically, MySQL) and triggering the correct implementation?

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

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

Re: [Django] #29543: CPointerBase.__del__() crashes with ImportError

[Django]

#29543: CPointerBase.__del__() crashes with ImportError
+---
 Reporter:  Evandro Myller  |Owner:  Mushtaq Ali
 Type:  Bug |   Status:  assigned
Component:  GIS |  Version:  2.0
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  1   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+---

Comment (by Mushtaq Ali):

 Tim I have added the test.

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

Re: [Django] #29544: Add a MariaDB database backend

[Django]

#29544: Add a MariaDB database backend
-+-
 Reporter:  Michal Čihař |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Release blocker  |   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 Claude Paroz):

 * severity:  Normal => Release blocker


Comment:

 Even if it is not officially supported, I think we should do everything we
 can to not break it.
 I have sites in production with MariaDB!

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

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

Re: [Django] #29544: Add a MariaDB database backend

[Django]

#29544: Add a MariaDB database backend
-+-
 Reporter:  Michal Čihař |Owner:  nobody
 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
-+-

Comment (by Michal Čihař):

 The problem I see is that it worked just fine all versions up to 2.0.7 and
 it broke in 2.0.7 due to fix for MySQL 8.0. The other tickets seem to be
 about adding support for new features introduced by MariaDB, while this
 one is about fixing what used to work before.

 https://github.com/django/django/pull/10133 would work on 2.0 just fine in
 case you decide to use it as a fix.

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

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

Re: [Django] #29544: Add a MariaDB database backend (was: MariaDB regression in 2.0.7 in REGEXP_LIKE)

[Django]

#29544: Add a MariaDB database backend
-+-
 Reporter:  Michal Čihař |Owner:  nobody
 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 Tim Graham):

 * component:  Uncategorized => Database layer (models, ORM)
 * version:  2.0 => master
 * type:  Uncategorized => New feature
 * stage:  Unreviewed => Accepted


Comment:

 Django doesn't officially support MariaDB. There's been some
 [https://groups.google.com/d/topic/django-
 developers/31j1dNOZ7zc/discussion discussion] about adding support. There
 are some other tickets like #27676.

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

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

[Django] #29544: MariaDB regression in 2.0.7 in REGEXP_LIKE

[Django]

#29544: MariaDB regression in 2.0.7 in REGEXP_LIKE
-+
   Reporter:  Michal Čihař   |  Owner:  nobody
   Type:  Uncategorized  | Status:  new
  Component:  Uncategorized  |Version:  2.0
   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  |
-+
 Since Django 2.0.7 it fails to do regexp lookups on MariaDB. The problem
 is in code introduced for https://code.djangoproject.com/ticket/29451 - it
 assumes that MariaDB 10.3 has REGEXP_LIKE what is not true.

 The exception is:


 {{{
 Traceback (most recent call last):
   File "/home/travis/virtualenv/python3.6.3/lib/python3.6/site-
 packages/django/db/backends/utils.py", line 85, in _execute
 return self.cursor.execute(sql, params)
   File "/home/travis/virtualenv/python3.6.3/lib/python3.6/site-
 packages/django/db/backends/mysql/base.py", line 71, in execute
 return self.cursor.execute(query, args)
   File "/home/travis/virtualenv/python3.6.3/lib/python3.6/site-
 packages/MySQLdb/cursors.py", line 250, in execute
 self.errorhandler(self, exc, value)
   File "/home/travis/virtualenv/python3.6.3/lib/python3.6/site-
 packages/MySQLdb/connections.py", line 50, in defaulterrorhandler
 raise errorvalue
   File "/home/travis/virtualenv/python3.6.3/lib/python3.6/site-
 packages/MySQLdb/cursors.py", line 247, in execute
 res = self._query(query)
   File "/home/travis/virtualenv/python3.6.3/lib/python3.6/site-
 packages/MySQLdb/cursors.py", line 412, in _query
 rowcount = self._do_query(q)
   File "/home/travis/virtualenv/python3.6.3/lib/python3.6/site-
 packages/MySQLdb/cursors.py", line 375, in _do_query
 db.query(q)
   File "/home/travis/virtualenv/python3.6.3/lib/python3.6/site-
 packages/MySQLdb/connections.py", line 276, in query
 _mysql.connection.query(self, query)
 _mysql_exceptions.OperationalError: (1305, 'FUNCTION
 test_weblate.REGEXP_LIKE does not exist')
 }}}

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

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