Re: [Django] #28439: When() [on MySQL] does not work with models using UUID as primary key

#28439: When() [on MySQL] does not work with models using UUID as primary key -+- Reporter: Dominik Kozaczko |Owner: nobody Type: Bug | Status: new

[Django] #28439: When() [on MySQL] does not work with models using UUID as primary key

#28439: When() [on MySQL] does not work with models using UUID as primary key -+- Reporter: Dominik| Owner: nobody Kozaczko | Type: Bug|

Re: [Django] #28371: Cast generates invalid SQL for SQLite, PostgreSQL, and Oracle if max_length isn't provide to CharField

#28371: Cast generates invalid SQL for SQLite, PostgreSQL, and Oracle if max_length isn't provide to CharField -+- Reporter: James Doherty|Owner: felixxm Type: Bug

Re: [Django] #17522: ModelAdmin.ordering validation too strict

#17522: ModelAdmin.ordering validation too strict -+- Reporter: Sebastian Goll |Owner: nobody Type: Bug | Status: new Component: contrib.admin

Re: [Django] #28438: Initial migration creates fields not listed in the migration if mixin class changes

#28438: Initial migration creates fields not listed in the migration if mixin class changes -+- Reporter: Michal Dabski|Owner: nobody Type: Bug |

Re: [Django] #28363: Allow naming the migration generated by squashmigrations

#28363: Allow naming the migration generated by squashmigrations + Reporter: Melvyn Sopacua |Owner: nobody Type: New feature | Status: closed Component: Migrations

Re: [Django] #25253: MySQL migrations drop & recreate constraints unnecessarily when changing attributes that don't affect the schema

#25253: MySQL migrations drop & recreate constraints unnecessarily when changing attributes that don't affect the schema --+ Reporter: Thomas Recouvreux |Owner: nobody Type: Cleanup/opti

Re: [Django] #28216: Add next_page to LoginView

#28216: Add next_page to LoginView +-- Reporter: ThinkChaos |Owner: ThinkChaos Type: New feature | Status: assigned Component: contrib.auth|

Re: [Django] #28438: Initial migration creates fields not listed in the migration if mixin class changes

#28438: Initial migration creates fields not listed in the migration if mixin class changes -+- Reporter: Michal Dabski|Owner: nobody Type: Uncategorized|

Re: [Django] #28438: Initial migration creates fields not listed in the migration if mixin class changes

#28438: Initial migration creates fields not listed in the migration if mixin class changes -+- Reporter: Michal Dabski|Owner: nobody Type: Uncategorized|

Re: [Django] #28438: Initial migration creates fields not listed in the migration if mixin class changes

#28438: Initial migration creates fields not listed in the migration if mixin class changes ---+-- Reporter: Michal Dabski |Owner: nobody Type: Uncategorized | Status: new

[Django] #28438: Initial migration creates fields not listed in the migration if mixin class changes

#28438: Initial migration creates fields not listed in the migration if mixin class changes -+ Reporter: Michal Dabski | Owner: nobody Type: Uncategorized | Status: new

Re: [Django] #7554: python manage.py dbshell does not enter password from settings.py

#7554: python manage.py dbshell does not enter password from settings.py -+- Reporter: Kaell|Owner: nobody Type: Uncategorized| Status: closed Component:

Re: [Django] #7554: python manage.py dbshell does not enter password from settings.py

#7554: python manage.py dbshell does not enter password from settings.py -+- Reporter: Kaell|Owner: nobody Type: Uncategorized| Status: closed Component:

Re: [Django] #28433: comparing GEOSGeometry with non-canonical WKT string return False

#28433: comparing GEOSGeometry with non-canonical WKT string return False -+- Reporter: Sergey Fedoseev |Owner: Sergey | Fedoseev Type: Bug

Re: [Django] #28437: add support of complex geometry expressions in GIS lookups

#28437: add support of complex geometry expressions in GIS lookups -+- Reporter: Sergey Fedoseev |Owner: Sergey Type: | Fedoseev Cleanup/optimization

Re: [Django] #28436: enable GIS distance lookups on MySQL

#28436: enable GIS distance lookups on MySQL -+- Reporter: Sergey Fedoseev |Owner: Sergey | Fedoseev Type: New feature |

Re: [Django] #28437: add support of complex geometry expressions in GIS lookups

#28437: add support of complex geometry expressions in GIS lookups -+- Reporter: Sergey Fedoseev |Owner: Sergey Type: | Fedoseev Cleanup/optimization

Re: [Django] #28437: add support of complex geometry expressions in GIS lookups

#28437: add support of complex geometry expressions in GIS lookups -+- Reporter: Sergey Fedoseev |Owner: nobody Type: | Status: new Cleanup/opt

[Django] #28437: add support of complex geometry expressions in GIS lookups

#28437: add support of complex geometry expressions in GIS lookups + Reporter: Sergey Fedoseev | Owner: nobody Type: Cleanup/optimization | Status: new

Re: [Django] #28436: enable GIS distance lookups on MySQL

#28436: enable GIS distance lookups on MySQL -+- Reporter: Sergey Fedoseev |Owner: Sergey | Fedoseev Type: New feature |

Re: [Django] #28436: enable GIS distance lookups on MySQL

#28436: enable GIS distance lookups on MySQL -+- Reporter: Sergey Fedoseev |Owner: Sergey | Fedoseev Type: New feature |

[Django] #28436: enable GIS distance lookups on MySQL

#28436: enable GIS distance lookups on MySQL ---+ Reporter: Sergey Fedoseev | Owner: nobody Type: New feature | Status: new Component: GIS |

Re: [Django] #28433: comparing GEOSGeometry with non-canonical WKT string return False

#28433: comparing GEOSGeometry with non-canonical WKT string return False -+- Reporter: Sergey Fedoseev |Owner: Sergey | Fedoseev Type: Bug