Re: [Django] #5069: newforms cannot initial SelectDateWidget 's value

2020-02-10 Thread Django
#5069: newforms cannot initial SelectDateWidget 's value ---+-- Reporter: anonymous |Owner: nobody Type: Uncategorized | Status: closed Component: Uncategorized |

Re: [Django] #31255: Migrations create a redundant RemoveField operation when deleting 2 models with related fields. (was: Migration optimizer removes 1 RemoveField for FK when deleting 2 models)

2020-02-10 Thread Django
#31255: Migrations create a redundant RemoveField operation when deleting 2 models with related fields. --+ Reporter: Panagis Alisandratos |Owner: nobody Type: Cleanup/optimization |

Re: [Django] #31256: Inline widget permision is now based on it's foregin key.

2020-02-10 Thread Django
#31256: Inline widget permision is now based on it's foregin key. +-- Reporter: John Lyu|Owner: nobody Type: Uncategorized | Status: closed

Re: [Django] #31256: Inline widget permision is now based on it's foregin key.

2020-02-10 Thread Django
#31256: Inline widget permision is now based on it's foregin key. +-- Reporter: PaleNeutron |Owner: nobody Type: Uncategorized | Status: new Component:

Re: [Django] #31256: Inline widget permision is now based on it's foregin key.

2020-02-10 Thread Django
#31256: Inline widget permision is now based on it's foregin key. +-- Reporter: PaleNeutron |Owner: nobody Type: Uncategorized | Status: new Component:

Re: [Django] #31256: Inline widget permision is now based on it's foregin key.

2020-02-10 Thread Django
#31256: Inline widget permision is now based on it's foregin key. +-- Reporter: PaleNeutron |Owner: nobody Type: Uncategorized | Status: new Component:

[Django] #31256: Inline widget permision is now based on it's foregin key.

2020-02-10 Thread Django
#31256: Inline widget permision is now based on it's foregin key. -+- Reporter: | Owner: nobody PaleNeutron| Type: | Status:

Re: [Django] #30509: Various FileResponse fixes and changes

2020-02-10 Thread Django
#30509: Various FileResponse fixes and changes --+ Reporter: Piotr Kunicki |Owner: nobody Type: Cleanup/optimization | Status: new Component: HTTP handling

Re: [Django] #31255: Migration optimizer removes 1 RemoveField for FK when deleting 2 models (was: Migration optimizer retains 1 RemoveField for FK when deleting 2 models)

2020-02-10 Thread Django
#31255: Migration optimizer removes 1 RemoveField for FK when deleting 2 models -+- Reporter: Palisand |Owner: nobody Type: | Status: new

Re: [Django] #31255: Migration optimizer retains 1 RemoveField for FK when deleting 2 models (was: Migration optimizer retains a 1 RemoveField for FK when deleting 2 models)

2020-02-10 Thread Django
#31255: Migration optimizer retains 1 RemoveField for FK when deleting 2 models -+- Reporter: Palisand |Owner: nobody Type: | Status: new

[Django] #31255: Migration optimizer retains a 1 RemoveField for FK when deleting 2 models

2020-02-10 Thread Django
#31255: Migration optimizer retains a 1 RemoveField for FK when deleting 2 models -+- Reporter: Palisand | Owner: nobody Type: | Status: new

Re: [Django] #31254: "populate() isn't reentrant" masks underlying error

2020-02-10 Thread Django
#31254: "populate() isn't reentrant" masks underlying error --+-- Reporter: TK-23 |Owner: nobody Type: Bug | Status: new Component: Core (Other) |

[Django] #31254: "populate() isn't reentrant" masks underlying error

2020-02-10 Thread Django
#31254: "populate() isn't reentrant" masks underlying error -+ Reporter: TK-23 | Owner: nobody Type: Uncategorized | Status: new Component: Core (Other)

Re: [Django] #31253: Possible data loss when using caching from async code.

2020-02-10 Thread Django
#31253: Possible data loss when using caching from async code. -+- Reporter: felixxm |Owner: Jon | Dufresne Type: Bug |

[Django] #31253: Possible data loss when using caching from async code.

2020-02-10 Thread Django
#31253: Possible data loss when using caching from async code. -+- Reporter: felixxm| Owner: Jon Dufresne Type: Bug| Status: assigned Component:

Re: [Django] #5069: newforms cannot initial SelectDateWidget 's value

2020-02-10 Thread Django
#5069: newforms cannot initial SelectDateWidget 's value ---+-- Reporter: anonymous |Owner: nobody Type: Uncategorized | Status: new Component: Uncategorized |

Re: [Django] #30846: postgis backend doesn't respect custom index names.

2020-02-10 Thread Django
#30846: postgis backend doesn't respect custom index names. -+- Reporter: Thomas Steen |Owner: Pratik Rasmussen | Kumar Type: Bug |

Re: [Django] #31251: QuerySet.annotate() crashes when grouping by OuterRef().

2020-02-10 Thread Django
#31251: QuerySet.annotate() crashes when grouping by OuterRef(). -+- Reporter: Oliver Ford |Owner: Yuri Type: | Savin Cleanup/optimization |

Re: [Django] #31251: QuerySet.annotate() crashes when grouping by OuterRef().

2020-02-10 Thread Django
#31251: QuerySet.annotate() crashes when grouping by OuterRef(). -+- Reporter: Oliver Ford |Owner: Yuri Type: | Savin Cleanup/optimization |

Re: [Django] #31250: assertXMLEqual() crashes on processing instructions.

2020-02-10 Thread Django
#31250: assertXMLEqual() crashes on processing instructions. ---+-- Reporter: Matt Fisher|Owner: Yuri Savin Type: Bug| Status: assigned Component:

Re: [Django] #31251: QuerySet.annotate() crashes when grouping by OuterRef().

2020-02-10 Thread Django
#31251: QuerySet.annotate() crashes when grouping by OuterRef(). -+- Reporter: Oliver Ford |Owner: Yuri Type: | Savin Cleanup/optimization |

Re: [Django] #31251: QuerySet.annotate() crashes when grouping by OuterRef(). (was: Unable to annotate a query that has an OuterRef already)

2020-02-10 Thread Django
#31251: QuerySet.annotate() crashes when grouping by OuterRef(). -+- Reporter: Oliver Ford |Owner: nobody Type: | Status: new

Re: [Django] #31250: assertXMLEqual() crashes on processing instructions. (was: assertXMLEqual fails on processing instructions)

2020-02-10 Thread Django
#31250: assertXMLEqual() crashes on processing instructions. ---+ Reporter: Matt Fisher|Owner: nobody Type: Bug| Status: new Component: Testing

Re: [Django] #30846: postgis backend doesn't respect custom index names.

2020-02-10 Thread Django
#30846: postgis backend doesn't respect custom index names. -+- Reporter: Thomas Steen |Owner: Pratik Rasmussen | Kumar Type: Bug |

Re: [Django] #31251: Unable to annotate a query that has an OuterRef already

2020-02-10 Thread Django
#31251: Unable to annotate a query that has an OuterRef already -+- Reporter: OJFord |Owner: nobody Type: Bug | Status: new Component:

[Django] #31252: Oracle GIS doesn't support spatial indexes in Meta.indexes.

2020-02-10 Thread Django
#31252: Oracle GIS doesn't support spatial indexes in Meta.indexes. + Reporter: felixxm | Owner: nobody Type: Bug | Status: new Component: GIS |

[Django] #31251: Unable to annotate a query that has an OuterRef already

2020-02-10 Thread Django
#31251: Unable to annotate a query that has an OuterRef already -+- Reporter: OJFord | Owner: nobody Type: Bug| Status: new Component: Database

Re: [Django] #31248: Missing whitespace in SQL generated for PostGIS indexed with USING.

2020-02-10 Thread Django
#31248: Missing whitespace in SQL generated for PostGIS indexed with USING. -+- Reporter: Hannes Ljungberg |Owner: Hannes Type: | Ljungberg Cleanup/optimization

Re: [Django] #31003: Suggesting: Documentation update for bulk_create method

2020-02-10 Thread Django
#31003: Suggesting: Documentation update for bulk_create method -+- Reporter: Peter Vlasveld |Owner: Adam Type: | (Chainz) Johnson Cleanup/optimization