Re: [Django] #27458: Oracle backend giving ORA-00911 : Invalid Character, querying with a literal "%s"

2017-11-14 Thread Django
#27458: Oracle backend giving ORA-00911 : Invalid Character, querying with a literal "%s" -+- Reporter: Gabriel Canto de |Owner: Andrew Souza | Nester Type

Re: [Django] #27843: M2M db table names with explicit `username`

2017-11-14 Thread Django
#27843: M2M db table names with explicit `username` -+- Reporter: felixxm |Owner: felixxm Type: Bug | Status: closed Component: Database

Re: [Django] #28792: Index names can be incorrectly truncated when using a namespaced table name

2017-11-14 Thread Django
#28792: Index names can be incorrectly truncated when using a namespaced table name -+- Reporter: Simon Charette |Owner: Simon | Charette Type: B

Re: [Django] #27458: Oracle backend giving ORA-00911 : Invalid Character, querying with a literal "%s"

2017-11-14 Thread Django
#27458: Oracle backend giving ORA-00911 : Invalid Character, querying with a literal "%s" -+- Reporter: Gabriel Canto de |Owner: Andrew Souza | Nester Type

Re: [Django] #27843: M2M db table names with explicit `username`

2017-11-14 Thread Django
#27843: M2M db table names with explicit `username` -+- Reporter: felixxm |Owner: felixxm Type: Bug | Status: closed Component: Database

Re: [Django] #28792: Index names can be incorrectly truncated when using a namespaced table name

2017-11-14 Thread Django
#28792: Index names can be incorrectly truncated when using a namespaced table name -+- Reporter: Simon Charette |Owner: Simon | Charette Type: B

Re: [Django] #470: [patch] "default" values should be expressed in SQL schema

2017-11-14 Thread Django
#470: [patch] "default" values should be expressed in SQL schema -+- Reporter: jws |Owner: nobody Type: enhancement | Status: closed Componen

Re: [Django] #20414: Handling of numbers under oracle is slow

2017-11-14 Thread Django
#20414: Handling of numbers under oracle is slow -+- Reporter: Shai Berger |Owner: Shai | Berger Type: Bug |

Re: [Django] #28542: migration that introduces uuid field is not reversible with unique=True

2017-11-14 Thread Django
#28542: migration that introduces uuid field is not reversible with unique=True +-- Reporter: karyon |Owner: Tim Martin Type: Bug | Status: assigned Component: M

Re: [Django] #28779: Customizing REDIRECT_FIELD_NAME is cumbersome (was: PasswordChangeView and PasswordChangeDoneView do not use a custom REDIRECT_FIELD_NAME)

2017-11-14 Thread Django
#28779: Customizing REDIRECT_FIELD_NAME is cumbersome --+ Reporter: Meiyer|Owner: nobody Type: Cleanup/optimization | Status: new Component: contrib.

Re: [Django] #28794: tx_isolation deprecation warning with MySQL 5.7.20+

2017-11-14 Thread Django
#28794: tx_isolation deprecation warning with MySQL 5.7.20+ -+- Reporter: JC |Owner: Sergey Type: | Fedoseev Cleanup/optimization |

Re: [Django] #28796: reverse() coerces bytes in args/kwargs to str which adds "b" prefixes to the ouput (was: django.utils.http.urlsafe_base64_encode() broken in Django 2.0)

2017-11-14 Thread Django
#28796: reverse() coerces bytes in args/kwargs to str which adds "b" prefixes to the ouput -+-- Reporter: Nick |Owner: nobody Type: Bug | Status: new Componen

Re: [Django] #20414: Handling of numbers under oracle is slow

2017-11-14 Thread Django
#20414: Handling of numbers under oracle is slow -+- Reporter: Shai Berger |Owner: Shai | Berger Type: Bug |

Re: [Django] #20414: Handling of numbers under oracle is slow

2017-11-14 Thread Django
#20414: Handling of numbers under oracle is slow -+- Reporter: Shai Berger |Owner: Shai | Berger Type: Bug |

Re: [Django] #28794: tx_isolation deprecation warning with MySQL 5.7.20+

2017-11-14 Thread Django
#28794: tx_isolation deprecation warning with MySQL 5.7.20+ -+- Reporter: JC |Owner: Sergey Type: | Fedoseev Cleanup/optimization |

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

2017-11-14 Thread Django
#28643: Complete the ORM Function Library -+- Reporter: Matthew Pava |Owner: JunyiJ Type: New feature | Status: assigned Component: Database layer

Re: [Django] #28560: distinct() on ordered queryset with restricted list of columns returns incorrect result

2017-11-14 Thread Django
#28560: distinct() on ordered queryset with restricted list of columns returns incorrect result -+- Reporter: felixxm |Owner: (none) Type: Bug |

Re: [Django] #28796: django.utils.http.urlsafe_base64_encode() broken in Django 2.0

2017-11-14 Thread Django
#28796: django.utils.http.urlsafe_base64_encode() broken in Django 2.0 ---+-- Reporter: Nick |Owner: nobody Type: Bug| Status: new Component: Utilities |

Re: [Django] #28792: Index names can be incorrectly truncated when using a namespaced table name (was: Index names can be inapropriately truncated when using a namespaced table name)

2017-11-14 Thread Django
#28792: Index names can be incorrectly truncated when using a namespaced table name -+- Reporter: Simon Charette |Owner: Simon | Charette Type: B

Re: [Django] #28792: Index names can be inapropriately truncated when using a namespaced table name

2017-11-14 Thread Django
#28792: Index names can be inapropriately truncated when using a namespaced table name -+- Reporter: Simon Charette |Owner: Simon | Charette Type:

Re: [Django] #28796: django.utils.http.urlsafe_base64_encode() broken in Django 2.0

2017-11-14 Thread Django
#28796: django.utils.http.urlsafe_base64_encode() broken in Django 2.0 ---+-- Reporter: Nick |Owner: nobody Type: Bug| Status: new Component: Utilities |

Re: [Django] #28783: Support for custom operator class for indexes

2017-11-14 Thread Django
#28783: Support for custom operator class for indexes -+- Reporter: vinay karanam|Owner: nobody Type: New feature | Status: new Component: Database l

Re: [Django] #28789: Django won't update sqlite_master table using migrations.AlterModelTable, which causes loaddata to fail.

2017-11-14 Thread Django
#28789: Django won't update sqlite_master table using migrations.AlterModelTable, which causes loaddata to fail. -+- Reporter: Rafael Pires |Owner: nobody Type: Bug

Re: [Django] #28647: Add support for python-brace-format for variables within {% blocktrans %}

2017-11-14 Thread Django
#28647: Add support for python-brace-format for variables within {% blocktrans %} -+- Reporter: Aidas Bendoraitis|Owner: nobody Type: New feature | Status: n

Re: [Django] #28794: tx_isolation deprecation warning with MySQL 5.7.20+ (was: @@tx_isolation is deprecated warning in django/db/backends/mysql/base.py:71)

2017-11-14 Thread Django
#28794: tx_isolation deprecation warning with MySQL 5.7.20+ -+- Reporter: JC |Owner: Sergey Type: | Fedoseev Cleanup/optimization |

Re: [Django] #28786: Document middleware ordering considerations due to CommonMiddleware setting Content-Length

2017-11-14 Thread Django
#28786: Document middleware ordering considerations due to CommonMiddleware setting Content-Length -+- Reporter: spudnica |Owner: nobody Type: |

Re: [Django] #28786: Document middleware ordering considerations due to CommonMiddleware setting Content-Length

2017-11-14 Thread Django
#28786: Document middleware ordering considerations due to CommonMiddleware setting Content-Length -+- Reporter: spudnica |Owner: nobody Type: |

Re: [Django] #28786: Document middleware ordering considerations due to CommonMiddleware setting Content-Length

2017-11-14 Thread Django
#28786: Document middleware ordering considerations due to CommonMiddleware setting Content-Length -+- Reporter: spudnica |Owner: nobody Type: |

Re: [Django] #28794: @@tx_isolation is deprecated warning in django/db/backends/mysql/base.py:71

2017-11-14 Thread Django
#28794: @@tx_isolation is deprecated warning in django/db/backends/mysql/base.py:71 -+- Reporter: JC |Owner: Sergey | Fedoseev Type:

Re: [Django] #28791: ManagementUtility.execute() does not handle ImportError for invalid settings module

2017-11-14 Thread Django
#28791: ManagementUtility.execute() does not handle ImportError for invalid settings module -+- Reporter: Marten Kenbeek |Owner: nobody Type: | S

Re: [Django] #28744: enctype on if FileField

2017-11-14 Thread Django
#28744: enctype on if FileField + Reporter: Thomas Güttler |Owner: nobody Type: New feature | Status: closed Component: Forms | Version:

Re: [Django] #28744: enctype on if FileField

2017-11-14 Thread Django
#28744: enctype on if FileField + Reporter: Thomas Güttler |Owner: nobody Type: New feature | Status: new Component: Forms | Version: ma

Re: [Django] #28795: Remove 'not in' checks and use dict.setdefault()

2017-11-14 Thread Django
#28795: Remove 'not in' checks and use dict.setdefault() -+- Reporter: Дилян Палаузов |Owner: nobody Type: | Status: closed Cleanup/optimizati

Re: [Django] #28795: Remove 'not in' checks and use dict.setdefault() (was: Utilize dict.setdefault())

2017-11-14 Thread Django
#28795: Remove 'not in' checks and use dict.setdefault() -+- Reporter: Дилян Палаузов |Owner: nobody Type: | Status: new Cleanup/optimization

Re: [Django] #28797: Sum aggregation might return "-0.00" instead of "0.00"

2017-11-14 Thread Django
#28797: Sum aggregation might return "-0.00" instead of "0.00" -+- Reporter: Simon Hanna |Owner: nobody Type: Bug | Status: new Component: D

Re: [Django] #6498: Add case insensitive model ordering

2017-11-14 Thread Django
#6498: Add case insensitive model ordering -+- Reporter: Bastian Kleineidam |Owner: nobody | Type: New feature | Status: closed C

Re: [Django] #28797: Sum aggregation might return "-0.00" instead of "0.00"

2017-11-14 Thread Django
#28797: Sum aggregation might return "-0.00" instead of "0.00" -+- Reporter: Simon Hanna |Owner: nobody Type: Bug | Status: new Component: D

Re: [Django] #28797: Sum aggregation might return "-0.00" instead of "0.00" (was: Sum aggregation might return "-0.00" instead of None)

2017-11-14 Thread Django
#28797: Sum aggregation might return "-0.00" instead of "0.00" -+- Reporter: Simon Hanna |Owner: nobody Type: Bug | Status: new Component: D

[Django] #28797: Sum aggregation might return "-0.00" instead of None

2017-11-14 Thread Django
#28797: Sum aggregation might return "-0.00" instead of None -+- Reporter: simhnna| Owner: nobody Type: Bug| Status: new Component: Database |

Re: [Django] #470: [patch] "default" values should be expressed in SQL schema

2017-11-14 Thread Django
#470: [patch] "default" values should be expressed in SQL schema -+- Reporter: jws |Owner: nobody Type: enhancement | Status: closed Componen

Re: [Django] #28000: Avoid SET/DROP DEFAULT unless a field changes from null to non-null

2017-11-14 Thread Django
#28000: Avoid SET/DROP DEFAULT unless a field changes from null to non-null -+- Reporter: Matteo Pietro Russo |Owner: nobody Type: | Status: closed

Re: [Django] #28540: When you save three or more ImageField in admin file perm = 0o600

2017-11-14 Thread Django
#28540: When you save three or more ImageField in admin file perm = 0o600 -+- Reporter: Yaroslav Demidenko |Owner: nobody Type: Bug | Status: closed

Re: [Django] #28796: django.utils.http.urlsafe_base64_encode() broken in Django 2.0

2017-11-14 Thread Django
#28796: django.utils.http.urlsafe_base64_encode() broken in Django 2.0 ---+-- Reporter: Nick |Owner: nobody Type: Bug| Status: new Component: Utilities |