[Django] #29635: can't pass int value to QueryDict Instance

#29635: can't pass int value to QueryDict Instance -+ Reporter: dhcn | Owner: nobody Type: Bug| Status: new Component: HTTP handling |

Re: [Django] #28668: Add ON CONFLICT IGNORE support to QuerySet.bulk_create()

#28668: Add ON CONFLICT IGNORE support to QuerySet.bulk_create() -+- Reporter: Tom Forbes |Owner: Tom | Forbes Type: New feature |

Re: [Django] #28668: Add ON CONFLICT IGNORE support to QuerySet.bulk_create()

#28668: Add ON CONFLICT IGNORE support to QuerySet.bulk_create() -+- Reporter: Tom Forbes |Owner: Tom | Forbes Type: New feature |

Re: [Django] #28668: Add ON CONFLICT IGNORE support to QuerySet.bulk_create() (was: Add ON CONFLICT support to QuerySet.bulk_create())

#28668: Add ON CONFLICT IGNORE support to QuerySet.bulk_create() -+- Reporter: Tom Forbes |Owner: Tom | Forbes Type: New feature |

Re: [Django] #28668: Add ON CONFLICT support to QuerySet.bulk_create()

#28668: Add ON CONFLICT support to QuerySet.bulk_create() -+- Reporter: Tom Forbes |Owner: Tom | Forbes Type: New feature |

Re: [Django] #29634: QueryDict fails to urlencode integer values

#29634: QueryDict fails to urlencode integer values ---+-- Reporter: Vitor Freitas |Owner: nobody Type: Bug| Status: closed Component: HTTP handling |

[Django] #29634: QueryDict fails to urlencode integer values

#29634: QueryDict fails to urlencode integer values -+ Reporter: Vitor Freitas | Owner: nobody Type: Bug| Status: new Component: HTTP handling |

Re: [Django] #28668: Add ON CONFLICT support to QuerySet.bulk_create()

#28668: Add ON CONFLICT support to QuerySet.bulk_create() -+- Reporter: Tom Forbes |Owner: Tom | Forbes Type: New feature |

Re: [Django] #29198: Add a --plan option to the migrate command

#29198: Add a --plan option to the migrate command -+- Reporter: Craig de Stigter |Owner: Calvin | DeBoer Type: New feature |

Re: [Django] #29628: createsuperuser does not validate password against username or other required fields

#29628: createsuperuser does not validate password against username or other required fields ---+- Reporter: Josh Schneier |Owner: Josh Schneier Type: Bug| Status:

Re: [Django] #28584: Remove workarounds for SQLite < 3.7.15

#28584: Remove workarounds for SQLite < 3.7.15 -+- Reporter: Sergey Fedoseev |Owner: nobody Type: | Status: closed Cleanup/optimization

Re: [Django] #28584: Remove workarounds for SQLite < 3.7.15

#28584: Remove workarounds for SQLite < 3.7.15 -+- Reporter: Sergey Fedoseev |Owner: nobody Type: | Status: closed Cleanup/optimization

Re: [Django] #29625: Make Model.refresh_from_db() clear prefetch related caches

#29625: Make Model.refresh_from_db() clear prefetch related caches -+- Reporter: Ming Qin |Owner: Ming Qin Type: | Status: assigned Cle

Re: [Django] #29625: Make Model.refresh_from_db() clear prefetch related caches (was: Expose RelatedManager._remove_prefetched_objects as public method)

#29625: Make Model.refresh_from_db() clear prefetch related caches -+- Reporter: Ming Qin |Owner: nobody Type: | Status: new Cleanup/op

Re: [Django] #29499: Race condition in QuerySet.update_or_create()

#29499: Race condition in QuerySet.update_or_create() -+- Reporter: Michael Sanders |Owner: Michael | Sanders Type: Bug |

Re: [Django] #29376: admin adjustability improvement: Take into account `show_save_and_add_another` context var

#29376: admin adjustability improvement: Take into account `show_save_and_add_another` context var --+ Reporter: Mihas |Owner: nobody Type: Cleanup/optimization |

Re: [Django] #29226: @modify_settings append/remove/prepend is affected by dictionary order

#29226: @modify_settings append/remove/prepend is affected by dictionary order -+- Reporter: Manuel Kaufmann |Owner: | benjaoming Type: Bug

Re: [Django] #29547: Support for partial/filtered indexes

#29547: Support for partial/filtered indexes -+- Reporter: Mads Jensen |Owner: nobody Type: New feature | Status: new Component: Database layer

Re: [Django] #29624: Django 2.1 incompatible with sqlite 3.6.20

#29624: Django 2.1 incompatible with sqlite 3.6.20 -+- Reporter: zsblevins|Owner: nobody Type: Bug | Status: closed Component: Database l

Re: [Django] #28584: Remove workarounds for SQLite < 3.7.15

#28584: Remove workarounds for SQLite < 3.7.15 -+- Reporter: Sergey Fedoseev |Owner: nobody Type: | Status: closed Cleanup/optimization

Re: [Django] #29631: Feature Request: models.UniqueBooleanField()

#29631: Feature Request: models.UniqueBooleanField() -+- Reporter: Michael |Owner: nobody Type: New feature | Status: closed Component: Database

Re: [Django] #29633: Document the geometry type for each GeoDjango model field

#29633: Document the geometry type for each GeoDjango model field -+- Reporter: Danilo Bargen|Owner: nobody Type: Bug | Status: closed Compone

Re: [Django] #29633: Document the geometry type for each GeoDjango model field

#29633: Document the geometry type for each GeoDjango model field -+- Reporter: Danilo Bargen|Owner: nobody Type: Bug | Status: closed Compone

Re: [Django] #29633: Document the geometry type for each GeoDjango model field (was: GeoDjango model fields are undocumented)

#29633: Document the geometry type for each GeoDjango model field -+- Reporter: Danilo Bargen|Owner: nobody Type: Bug | Status: new Component:

Re: [Django] #28766: Add route information to ResolverMatch

#28766: Add route information to ResolverMatch -+- Reporter: Benjamin Wohlwend|Owner: Melvyn | Sopacua Type: New feature |

Re: [Django] #29632: After migrating a Django project from Python 2 to 3, db migration of django.contrib.sites fails with "TypeError: attribute name must be string, not 'bytes'"

#29632: After migrating a Django project from Python 2 to 3, db migration of django.contrib.sites fails with "TypeError: attribute name must be string, not 'bytes'" -+- Reporter: Florian Mayer|

Re: [Django] #28766: Add route information to ResolverMatch

#28766: Add route information to ResolverMatch ---+ Reporter: Benjamin Wohlwend |Owner: mes3yd Type: New feature| Status: assigned Component: Core (URLs)

Re: [Django] #14296: 'manage.py test' failing for apps that access read-only databases

#14296: 'manage.py test' failing for apps that access read-only databases ---+ Reporter: kthhrv |Owner: nobody Type: Bug| Status: new Component

Re: [Django] #29633: GeoDjango model fields are undocumented

#29633: GeoDjango model fields are undocumented +-- Reporter: Danilo Bargen |Owner: nobody Type: Bug | Status: new Component: Documentation

Re: [Django] #29633: GeoDjango model fields are undocumented

#29633: GeoDjango model fields are undocumented +-- Reporter: Danilo Bargen |Owner: nobody Type: Bug | Status: new Component: Documentation

[Django] #29633: GeoDjango model fields are undocumented

#29633: GeoDjango model fields are undocumented -+- Reporter: Danilo | Owner: nobody Bargen | Type: Bug| Status: new

Re: [Django] #29632: After migrating a Django project from Python 2 to 3, db migration of django.contrib.sites fails with "TypeError: attribute name must be string, not 'bytes'"

#29632: After migrating a Django project from Python 2 to 3, db migration of django.contrib.sites fails with "TypeError: attribute name must be string, not 'bytes'" -+- Reporter: Florian Mayer|

Re: [Django] #29632: After migrating a Django project from Python 2 to 3, db migration of django.contrib.sites fails with "TypeError: attribute name must be string, not 'bytes'"

#29632: After migrating a Django project from Python 2 to 3, db migration of django.contrib.sites fails with "TypeError: attribute name must be string, not 'bytes'" -+- Reporter: Florian Mayer|

Re: [Django] #29631: Feature Request: models.UniqueBooleanField()

#29631: Feature Request: models.UniqueBooleanField() -+- Reporter: Michael |Owner: nobody Type: New feature | Status: closed Component: Database

[Django] #29632: After migrating a Django project from Python 2 to 3, db migration of django.contrib.sites fails with "TypeError: attribute name must be string, not 'bytes'"

#29632: After migrating a Django project from Python 2 to 3, db migration of django.contrib.sites fails with "TypeError: attribute name must be string, not 'bytes'" -+- Reporter: Florian| Owner: no

Re: [Django] #29613: Allow --keepdb to work on PostgreSQL if the database exists but the user can't create databases

#29613: Allow --keepdb to work on PostgreSQL if the database exists but the user can't create databases -+- Reporter: Paul McDermott |Owner: felixxm Type: Bug |

Re: [Django] #29613: Allow --keepdb to work on PostgreSQL if the database exists but the user can't create databases

#29613: Allow --keepdb to work on PostgreSQL if the database exists but the user can't create databases -+- Reporter: Paul McDermott |Owner: felixxm Type: Bug |