Re: [Django] #28198: Model attributes shouldn't override deferred fields

2017-11-04 Thread Django
#28198: Model attributes shouldn't override deferred fields -+- Reporter: Ryan Hiebert |Owner: | Denis.Tarykin Type: Bug |

Re: [Django] #17448: Error reading PointField in objects.raw(sql) query

2017-11-04 Thread Django
#17448: Error reading PointField in objects.raw(sql) query -+ Reporter: oluckyman|Owner: David Eklund Type: Bug | Status: closed Component: GIS |

Re: [Django] #28518: improve performance of loading geometries from DB

2017-11-04 Thread Django
#28518: improve performance of loading geometries from DB -+- Reporter: Sergey Fedoseev |Owner: Sergey Type: | Fedoseev Cleanup/optimization |

Re: [Django] #28632: Manager.raw() crashes if the model has GIS fields

2017-11-04 Thread Django
#28632: Manager.raw() crashes if the model has GIS fields -+- Reporter: gcbirzan |Owner: Sergey | Fedoseev Type: Bug |

Re: [Django] #28404: Django admin empty_value/empty_value_display doesn't check for empty strings

2017-11-04 Thread Django
#28404: Django admin empty_value/empty_value_display doesn't check for empty strings -+- Reporter: Mark Koh |Owner: Nazarov | Georgiy Type:

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

2017-11-04 Thread Django
#28766: Add route information to ResolverMatch -+- Reporter: Benjamin Wohlwend|Owner: Benjamin | Wohlwend Type: New feature |

Re: [Django] #11964: Add the ability to use database-level CHECK CONSTRAINTS

2017-11-04 Thread Django
#11964: Add the ability to use database-level CHECK CONSTRAINTS -+- Reporter: Matthew Schinckel|Owner: Ian Foote Type: New feature | Status: assigned

Re: [Django] #28632: Manager.raw() crashes if the model has GIS fields

2017-11-04 Thread Django
#28632: Manager.raw() crashes if the model has GIS fields -+- Reporter: gcbirzan |Owner: Sergey | Fedoseev Type: Bug |

Re: [Django] #17448: Error reading PointField in objects.raw(sql) query

2017-11-04 Thread Django
#17448: Error reading PointField in objects.raw(sql) query -+ Reporter: oluckyman|Owner: David Eklund Type: Bug | Status: closed Component: GIS |

Re: [Django] #28518: improve performance of loading geometries from DB

2017-11-04 Thread Django
#28518: improve performance of loading geometries from DB -+- Reporter: Sergey Fedoseev |Owner: Sergey Type: | Fedoseev Cleanup/optimization |

Re: [Django] #28764: Store staticfiles.json with code

2017-11-04 Thread Django
#28764: Store staticfiles.json with code -+- Reporter: Kevin Christopher|Owner: nobody Henry | Type: | Status:

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

2017-11-04 Thread Django
#28766: Add route information to ResolverMatch -+- Reporter: Benjamin Wohlwend|Owner: Benjamin | Wohlwend Type: New feature |

Re: [Django] #28767: Incorrect value when annotating empty list as Value() on ArrayField.

2017-11-04 Thread Django
#28767: Incorrect value when annotating empty list as Value() on ArrayField. ---+ Reporter: Matthew Schinckel |Owner: (none) Type: Bug| Status: new

Re: [Django] #28762: Can't aggregate annotations with array parameters

2017-11-04 Thread Django
#28762: Can't aggregate annotations with array parameters -+- Reporter: Daniel Keller|Owner: (none) Type: Bug | Status: new Component:

[Django] #28770: Warn that quoting a placeholder in a raw SQL string can lead to SQL injection

2017-11-04 Thread Django
#28770: Warn that quoting a placeholder in a raw SQL string can lead to SQL injection + Reporter: Hynek Cernoch | Owner: nobody Type: Cleanup/optimization |

Re: [Django] #28752: django.setup() should not be runnable multiple times

2017-11-04 Thread Django
#28752: django.setup() should not be runnable multiple times +-- Reporter: pascal chambon |Owner: nobody Type: Bug | Status: new Component: Core (Other)

[Django] #28769: Utilize 'x or y' in place of 'x if x else y'

2017-11-04 Thread Django
#28769: Utilize 'x or y' in place of 'x if x else y' --+ Reporter: Дилян Палаузов | Owner: nobody Type: Uncategorized | Status: new Component: Uncategorized |

Re: [Django] #28769: Utilize 'x or y' in place of 'x if x else y'

2017-11-04 Thread Django
#28769: Utilize 'x or y' in place of 'x if x else y' -+- Reporter: Дилян Палаузов |Owner: nobody Type: | Status: new Cleanup/optimization

Re: [Django] #28769: Utilize 'x or y' in place of 'x if x else y'

2017-11-04 Thread Django
#28769: Utilize 'x or y' in place of 'x if x else y' -+- Reporter: Дилян Палаузов |Owner: nobody Type: | Status: new Cleanup/optimization

Re: [Django] #28770: Warn that quoting a placeholder in a raw SQL string can lead to SQL injection

2017-11-04 Thread Django
#28770: Warn that quoting a placeholder in a raw SQL string can lead to SQL injection --+ Reporter: Hynek Cernoch |Owner: nobody Type: Cleanup/optimization |