Re: [Django] #20226: Django problematic when Oracle when column/table names are mixed case

#20226: Django problematic when Oracle when column/table names are mixed case -+- Reporter: calcium |Owner: nobody Type: Bug | Status: new

[Django] #20227: Accept an empty SECRET_KEY when DEBUG is True

#20227: Accept an empty SECRET_KEY when DEBUG is True ---+ Reporter: lsaffre| Owner: nobody Type: Uncategorized | Status: new Component: Uncategorized |Version: 1.5 Severity: Normal |

Re: [Django] #20226: Django problematic when Oracle when column/table names are mixed case

#20226: Django problematic when Oracle when column/table names are mixed case -+- Reporter: calcium |Owner: nobody Type: Bug | Status: new

[Django] #20226: Django problematic when Oracle when column/table names are mixed case

#20226: Django problematic when Oracle when column/table names are mixed case --+- Reporter: calcium | Owner: nobody Type: Bug | Status: new Component:

Re: [Django] #20225: query model using `filter` or `get` occur ValueError: invalid literal for int() with base 10

#20225: query model using `filter` or `get` occur ValueError: invalid literal for int() with base 10 -+- Reporter: 592280502@… |Owner: nobody Type: Bug |

[Django] #20225: query model using `filter` or `get` occur ValueError: invalid literal for int() with base 10

#20225: query model using `filter` or `get` occur ValueError: invalid literal for int() with base 10 -+ Reporter: 592280502@… | Owner: nobody Type: Bug | Status: new Component:

Re: [Django] #20147: Replace and deprecate request.META for HTTP headers

#20147: Replace and deprecate request.META for HTTP headers ---+-- Reporter: lukeplant |Owner: nobody Type: New feature| Status: new Component: HTTP handling |

Re: [Django] #19733: Deprecate ModelForm without explicit fields

#19733: Deprecate ModelForm without explicit fields -+- Reporter: aaugustin|Owner: lukeplant Type: | Status: assigned

Re: [Django] #19445: Fieldsets' validation doesn't call get_form

#19445: Fieldsets' validation doesn't call get_form ---+ Reporter: KJ |Owner: slurms Type: Bug| Status: new Component: contrib.admin |

Re: [Django] #20217: query model using `filter` or `get` occur ValueError: invalid literal for int() with base 10

#20217: query model using `filter` or `get` occur ValueError: invalid literal for int() with base 10 -+- Reporter: 592280502@… |Owner: nobody Type: Bug |

Re: [Django] #20222: Some functions are wrapped into allow_lazy incorrectly

#20222: Some functions are wrapped into allow_lazy incorrectly ---+-- Reporter: void |Owner: nobody Type: Bug| Status: new Component: Utilities |

[Django] #20224: Documentation fix of allow_lazy usage example

#20224: Documentation fix of allow_lazy usage example --+ Reporter: void | Owner: nobody Type: Cleanup/optimization | Status: new Component: Documentation |Version: master

[Django] #20223: Allow allow_lazy to be used as a decorator

#20223: Allow allow_lazy to be used as a decorator -+ Reporter: void | Owner: nobody Type: New feature | Status: new Component: Utilities|Version: master Severity: Normal | Keywords:

Re: [Django] #3591: add support for custom app_label and verbose_name

#3591: add support for custom app_label and verbose_name --+ Reporter: jkocherhans |Owner: adrian Type: New feature | Status: new Component: Core (Other) |

[Django] #20222: Some functions are wrapped into allow_lazy incorrectly

#20222: Some functions are wrapped into allow_lazy incorrectly + Reporter: void| Owner: nobody Type: Bug | Status: new Component: Utilities |Version: master Severity: Normal |

Re: [Django] #20147: Replace and deprecate request.META for HTTP headers

#20147: Replace and deprecate request.META for HTTP headers ---+-- Reporter: lukeplant |Owner: nobody Type: New feature| Status: new Component: HTTP handling |

[django/django] f69396: Fix admin_views tests after commit 3be368c73e.

Branch: refs/heads/master Home: https://github.com/django/django Commit: f69396665c1dd3b6b70cc053f16403c66d57ce60 https://github.com/django/django/commit/f69396665c1dd3b6b70cc053f16403c66d57ce60 Author: Baptiste Mispelon Date: 2013-04-08 (Mon, 08 Apr

Re: [Django] #14019: SQLInsertCompiler.as_sql() failure

#14019: SQLInsertCompiler.as_sql() failure -+- Reporter: mlavin |Owner: tobias Type: Bug | Status: closed Component: Database layer

[django/django] 161c4d: Fixed #14019 -- Initialize `SQLInsertCompiler.retu...

Branch: refs/heads/master Home: https://github.com/django/django Commit: 161c4da588d4cc757da44bcbb5875a84a7b8a7e6 https://github.com/django/django/commit/161c4da588d4cc757da44bcbb5875a84a7b8a7e6 Author: Tobias McNulty Date: 2013-04-08 (Mon, 08 Apr

Re: [Django] #14019: SQLInsertCompiler.as_sql() failure

#14019: SQLInsertCompiler.as_sql() failure -+- Reporter: mlavin |Owner: tobias Type: Bug | Status: new Component: Database layer

Re: [Django] #4136: NULL fields and Unique keys

#4136: NULL fields and Unique keys -+- Reporter: David Cramer |Owner: | aashu_dwivedi Type: Bug | Status:

Re: [Django] #14019: SQLInsertCompiler.as_sql() failure

#14019: SQLInsertCompiler.as_sql() failure -+- Reporter: mlavin |Owner: tobias Type: Bug | Status: new Component: Database layer

Re: [Django] #14019: SQLInsertCompiler.as_sql() failure

#14019: SQLInsertCompiler.as_sql() failure -+- Reporter: mlavin |Owner: tobias Type: Bug | Status: closed Component: Database layer

Re: [Django] #20221: `conditional_escape` does not work with lazy strings

#20221: `conditional_escape` does not work with lazy strings ---+- Reporter: bmispelon |Owner: bmispelon Type: Bug| Status: new Component: Utilities |

[django/django] 4a7292: Removed references to the DDN triage state.

Branch: refs/heads/master Home: https://github.com/django/django Commit: 4a7292df3be2338ff5d915a9ab3107067f662534 https://github.com/django/django/commit/4a7292df3be2338ff5d915a9ab3107067f662534 Author: Aymeric Augustin Date: 2013-04-08 (Mon, 08 Apr

Re: [Django] #20221: `conditional_escape` does not work with lazy strings

#20221: `conditional_escape` does not work with lazy strings ---+-- Reporter: bmispelon |Owner: bmispelon Type: Bug| Status: new Component: Utilities |

Re: [Django] #20220: Problems with databases

#20220: Problems with databases -+- Reporter: vallard.nyorx@… |Owner: nobody Type: Uncategorized| Status: closed Component: Uncategorized|

[Django] #20221: `conditional_escape` does not work with lazy strings

#20221: `conditional_escape` does not work with lazy strings +--- Reporter: bmispelon | Owner: bmispelon Type: Bug | Status: new Component: Utilities |Version: master Severity: Normal |

Re: [Django] #20220: Problems with databases

#20220: Problems with databases -+- Reporter: vallard.nyorx@… |Owner: nobody Type: Uncategorized| Status: new Component: Uncategorized|

[Django] #20220: Problems with databases

#20220: Problems with databases -+ Reporter: vallard.nyorx@… | Owner: nobody Type: Uncategorized| Status: new Component: Uncategorized|Version: 1.5 Severity: Normal |

Re: [Django] #15610: Generic Foreign Keys break when used with multi-db.

#15610: Generic Foreign Keys break when used with multi-db. --+ Reporter: legutierr |Owner: nobody Type: Bug | Status: new Component:

Re: [Django] #10134: unique_for_* broken?

#10134: unique_for_* broken? -+- Reporter: wdoekes |Owner: Alex Type: Uncategorized| Status: closed Component: Forms|

Re: [Django] #10134: unique_for_* broken?

#10134: unique_for_* broken? -+- Reporter: wdoekes |Owner: Alex Type: Uncategorized| Status: new Component: Forms|

Re: [Django] #20147: Replace and deprecate request.META for HTTP headers

#20147: Replace and deprecate request.META for HTTP headers ---+-- Reporter: lukeplant |Owner: nobody Type: New feature| Status: new Component: HTTP handling |

Re: [Django] #20219: block evaluation preceeds if-statement evaluation

#20219: block evaluation preceeds if-statement evaluation -+-- Reporter: djangobug@… |Owner: nobody Type: Bug | Status: closed Component: Template

Re: [Django] #20157: Cannot pickle prefetched queryset on model with callable default datetime.datetime.now

#20157: Cannot pickle prefetched queryset on model with callable default datetime.datetime.now -+- Reporter: thomaspurchas|Owner: nobody Type: Bug |

[Django] #20219: block evaluation preceeds if-statement evaluation

#20219: block evaluation preceeds if-statement evaluation -+ Reporter: djangobug@… | Owner: nobody Type: Bug | Status: new Component: Template system |Version: 1.4 Severity: Normal

Re: [Django] #20147: Replace and deprecate request.META for HTTP headers

#20147: Replace and deprecate request.META for HTTP headers ---+-- Reporter: lukeplant |Owner: nobody Type: New feature| Status: new Component: HTTP handling |

Re: [Django] #6702: ModelForm: assert given instance is instance of model

#6702: ModelForm: assert given instance is instance of model --+ Reporter: guettli |Owner: Type: Cleanup/optimization | Status: new Component: Forms

Re: [Django] #6702: ModelForm: assert given instance is instance of model

#6702: ModelForm: assert given instance is instance of model --+ Reporter: guettli |Owner: Type: Cleanup/optimization | Status: new Component: Forms

Re: [Django] #20209: fields is empty after post with RadioWidget

#20209: fields is empty after post with RadioWidget ---+-- Reporter: strelnikovdmitrij |Owner: nobody Type: Bug| Status: new Component: Forms

Re: [Django] #18098: order_with_respect_to should construct set_RELATED_order() method name from related_name

#18098: order_with_respect_to should construct set_RELATED_order() method name from related_name -+- Reporter: pressureman |Owner: nobody Type: Bug |

Re: [Django] #14018: Introduce class_plural %-substitution placeholder for related_name of ForeignKey/ManyToManyField

#14018: Introduce class_plural %-substitution placeholder for related_name of ForeignKey/ManyToManyField -+- Reporter: puxlit |Owner: nobody Type: New feature |

Re: [Django] #20111: Admin message levels are too ambigious

#20111: Admin message levels are too ambigious -+- Reporter: darklow |Owner: darklow Type: | Status: closed Cleanup/optimization

[django/django] 3be368: Fix #20111 Added more precise message level for su...

Branch: refs/heads/master Home: https://github.com/django/django Commit: 3be368c73e8e6696e7cc74421aeb4d06d8e828c8 https://github.com/django/django/commit/3be368c73e8e6696e7cc74421aeb4d06d8e828c8 Author: Kaspars Sprogis Date: 2013-04-08 (Mon, 08 Apr 2013)

Re: [Django] #20111: Admin message levels are too ambigious

#20111: Admin message levels are too ambigious -+- Reporter: darklow |Owner: darklow Type: | Status: assigned Cleanup/optimization

[Django] #20218: Default authorization backend returns False when queried for object level permissions

#20218: Default authorization backend returns False when queried for object level permissions ---+ Reporter: soren@…| Owner: nobody Type: Uncategorized | Status: new Component: Uncategorized |Version:

Re: [Django] #20099: Allow filtering 404 reports by user agent

#20099: Allow filtering 404 reports by user agent ---+ Reporter: coolRR |Owner: nobody Type: New feature| Status: new Component: HTTP handling |

Re: [Django] #20211: BoundField.label_tag now always escapes its `contents` parameter.

#20211: BoundField.label_tag now always escapes its `contents` parameter. -+- Reporter: bmispelon|Owner: bmispelon Type: Bug | Status: new Component:

Re: [Django] #20216: filtering over an Sum on a BooleanField uses BooleanField's get_db_prep_lookup on the value

#20216: filtering over an Sum on a BooleanField uses BooleanField's get_db_prep_lookup on the value -+- Reporter: Anossov |Owner: nobody Type: Bug |

Re: [Django] #20216: filtering over an Sum on a BooleanField uses BooleanField's get_db_prep_lookup on the value

#20216: filtering over an Sum on a BooleanField uses BooleanField's get_db_prep_lookup on the value -+- Reporter: Anossov |Owner: nobody Type: Bug |

[Django] #20217: query model using `filter` or `get` occur ValueError: invalid literal for int() with base 10

#20217: query model using `filter` or `get` occur ValueError: invalid literal for int() with base 10 --+ Reporter: 592280502@… | Owner: nobody Type: Bug | Status:

Re: [Django] #20216: filtering over an Sum on a BooleanField uses BooleanField's get_db_prep_lookup on the value

#20216: filtering over an Sum on a BooleanField uses BooleanField's get_db_prep_lookup on the value -+- Reporter: Anossov |Owner: nobody Type: Bug |