Re: [Django] #29478: cached_property decorator doesn't work with mangled method names

[Django]

#29478: cached_property decorator doesn't work with mangled method names
-+
 Reporter:  Thomas Grainger  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Utilities|  Version:  2.0
 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 Tim Graham):

 * needs_better_patch:  1 => 0


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

Re: [Django] #29630: Oracle crash querying multiple tables with the same column name when limit/offset is used.

[Django]

#29630: Oracle crash querying multiple tables with the same column name when
limit/offset is used.
-+-
 Reporter:  zelfor5436   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  2.1
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:  oracle, admin,   | Triage Stage:  Accepted
  exception  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Simon Charette):

 Since that would require quite invasive changes fixing do you believe it's
 worth fixing for 12.1? Maybe we could simply disable the ''feature'' on
 12.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/068.b0fd4077209e82fcba2d50f303ffe52a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29759: Add support for cx_Oracle 7

[Django]

#29759: Add support for cx_Oracle 7
-+-
 Reporter:  felixxm  |Owner:  felixxm
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  2.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  Oracle   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

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

Re: [Django] #27899: Phrase search query for Postgres full text search

[Django]

#27899: Phrase search query for Postgres full text search
-+-
 Reporter:  Ilya Semenov |Owner:  Greg
 |  Allensworth
 Type:  New feature  |   Status:  assigned
Component:  contrib.postgres |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Claude Paroz):

 * needs_better_patch:  1 => 0


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

Re: [Django] #29759: Add support for cx_Oracle 7

[Django]

#29759: Add support for cx_Oracle 7
-+-
 Reporter:  felixxm  |Owner:  felixxm
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  2.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  Oracle   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * has_patch:  0 => 1


Comment:

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

Re: [Django] #29738: Django can't serialize DateTimeTZRange(lower=None, upper=None, bounds='[)')

[Django]

#29738: Django can't serialize DateTimeTZRange(lower=None, upper=None, 
bounds='[)')
-+-
 Reporter:  Graham Mayer |Owner:  Can
 |  Sarıgöl
 Type:  Bug  |   Status:  assigned
Component:  contrib.postgres |  Version:  2.0
 Severity:  Normal   |   Resolution:
 Keywords:  rangefield   | Triage Stage:  Accepted
  postgresql psycopg2 migrations |
  removed|
Has patch:  0|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Can Sarıgöl):

 Can I change **serializer_factory** like this? so that all unserialized
 values can be tried to be available.


 {{{
 def serializer_factory(value):
 ...


 from django.utils.deconstruct import deconstructible
 deconstructible_value = deconstructible(
 value.__class__,
 path=value.__module__ + "." + value.__class__.__name__
 )
 value = deconstructible_value(value.__init__)
 return DeconstructableSerializer(value)

 raise ValueError(...)
 }}}

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

Re: [Django] #29758: Document testing custom error handlers

[Django]

#29758: Document testing custom error handlers
-+-
 Reporter:  Adam (Chainz)|Owner:  nobody
  Johnson|
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  2.1
 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 Carlton Gibson):

 * stage:  Unreviewed => Accepted


Comment:

 Yes. I've been down this road. Having this documented would be helpful I
 think.

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

[Django] #29759: Add support for cx_Oracle 7

[Django]

#29759: Add support for cx_Oracle 7
-+-
   Reporter:  felixxm|  Owner:  felixxm
   Type:  Bug| Status:  assigned
  Component:  Database   |Version:  2.1
  layer (models, ORM)|
   Severity:  Normal |   Keywords:  Oracle
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 The Oracle back-end doesn't work with `cx_Oracle=7.0.0`, example exception
 {{{
 File "django/db/backends/oracle/operations.py", line 229, in
 fetch_returned_insert_id
 return int(cursor._insert_id_var.getvalue())
 TypeError: int() argument must be a string, a bytes-like object or a
 number, not 'list'
 }}}

 It is caused by a following change:

 `14. When a DML returning statement is executed, variables bound to it
 will return an array when calling Variable.getvalue(). Attempts to set
 cx_Oracle.__future__.dml_ret_array_val are now ignored.`

 (see [https://cx-oracle.readthedocs.io/en/latest/releasenotes.html
 cx_Oracle 7 release notes]).

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

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

Re: [Django] #29630: Oracle crash querying multiple tables with the same column name when limit/offset is used.

[Django]

#29630: Oracle crash querying multiple tables with the same column name when
limit/offset is used.
-+-
 Reporter:  zelfor5436   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  2.1
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:  oracle, admin,   | Triage Stage:  Accepted
  exception  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Jani Tiainen):

 I I could reproduce issue with Oracle 12.1.0.2-se2

 I couldn't reproduce issue with Oracle 12.2.0.1-se2

 So it seems that issue has been fixed in Oracle 12.2

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