Re: [Django] #31144: MySQL unique constraints incorrectly limited to 255 char when it should be 1000.

#31144: MySQL unique constraints incorrectly limited to 255 char when it should be 1000. -+- Reporter: Steven Mapes |Owner: nobody Type: Bug | Sta

Re: [Django] #31144: MySQL unique constraints incorrectly limited to 255 char when it should be 1000.

#31144: MySQL unique constraints incorrectly limited to 255 char when it should be 1000. -+- Reporter: Steven Mapes |Owner: nobody Type: Bug | Sta

Re: [Django] #31162: GIS error logging when using WKT string as input to filter() query.

#31162: GIS error logging when using WKT string as input to filter() query. + Reporter: Arno|Owner: felixxm Type: Bug | Status: assigned Component: GIS |

[Django] #31170: dismissRelatedLookupPopup doesn't trigger change event

#31170: dismissRelatedLookupPopup doesn't trigger change event -+ Reporter: jdavid | Owner: nobody Type: Bug| Status: new Component: contrib.admi

Re: [Django] #31170: dismissRelatedLookupPopup doesn't trigger change event

#31170: dismissRelatedLookupPopup doesn't trigger change event -+-- Reporter: J. David Ibáñez |Owner: nobody Type: Bug | Status: closed Component: contrib.a

[Django] #31171: Documentation error in custom template tags

#31171: Documentation error in custom template tags + Reporter: Takayuki Hirayama | Owner: nobody Type: Cleanup/optimization | Status: new Component: Do

[Django] #31172: Wrong translation for "yes, no, maybe" in several .po files.

#31172: Wrong translation for "yes,no,maybe" in several .po files. + Reporter: José Antonio Ruiz | Owner: nobody Type: Bug | Status: new

Re: [Django] #31172: Wrong translation for "yes, no, maybe" in several .po files.

#31172: Wrong translation for "yes,no,maybe" in several .po files. -+- Reporter: José Antonio Ruiz|Owner: nobody Type: Bug | Status: new Component

Re: [Django] #31172: Wrong translation for "yes, no, maybe" in several .po files.

#31172: Wrong translation for "yes,no,maybe" in several .po files. -+- Reporter: José Antonio Ruiz|Owner: nobody Type: Bug | Status: new Component

Re: [Django] #31172: Wrong translation for "yes, no, maybe" in several .po files.

#31172: Wrong translation for "yes,no,maybe" in several .po files. -+- Reporter: José Antonio Ruiz|Owner: nobody Type: Bug | Status: new Component

Re: [Django] #31171: Documentation error in custom template tags

#31171: Documentation error in custom template tags -+- Reporter: Takayuki Hirayama|Owner: nobody Type: | Status: new Cleanup/optimization

Re: [Django] #31172: Wrong translation for "yes, no, maybe" in several .po files.

#31172: Wrong translation for "yes,no,maybe" in several .po files. -+- Reporter: José Antonio Ruiz|Owner: nobody Type: Bug | Status: new Component

Re: [Django] #31172: Wrong translation for "yes, no, maybe" in several .po files.

#31172: Wrong translation for "yes,no,maybe" in several .po files. ---+ Reporter: José Antonio Ruiz |Owner: nobody Type: Bug| Status: new Component: Temp

Re: [Django] #31172: Wrong translation for "yes, no, maybe" in several .po files.

#31172: Wrong translation for "yes,no,maybe" in several .po files. -+- Reporter: José Antonio Ruiz|Owner: José | Antonio Ruiz Type: Bug

Re: [Django] #31172: Wrong translation for "yes, no, maybe" in several .po files.

#31172: Wrong translation for "yes,no,maybe" in several .po files. -+- Reporter: José Antonio Ruiz|Owner: José | Antonio Ruiz Type: Bug

Re: [Django] #30765: cache_control() "max_age" overrides cache_page() "timeout"

#30765: cache_control() "max_age" overrides cache_page() "timeout" -+- Reporter: Danny Flack |Owner: Flavio | Curella Type: Bug

Re: [Django] #31162: GIS error logging when using WKT string as input to filter() query.

#31162: GIS error logging when using WKT string as input to filter() query. + Reporter: Arno|Owner: felixxm Type: Bug | Status: closed Component: GIS |

Re: [Django] #31171: Misleading wording in custom template tags docs. (was: Documentation error in custom template tags)

#31171: Misleading wording in custom template tags docs. -+- Reporter: Takayuki Hirayama|Owner: Takayuki Type: | Hirayama Cleanup/optimization |

Re: [Django] #30752: Allow using ExceptionReporter subclass in django.views.debug.technical_500_response

#30752: Allow using ExceptionReporter subclass in django.views.debug.technical_500_response -+- Reporter: Carlton Gibson |Owner: Pavel | Lysak Type

Re: [Django] #23951: SafeExceptionReporterFilter does not have a way to filter and redact exception messages

#23951: SafeExceptionReporterFilter does not have a way to filter and redact exception messages -+- Reporter: Lukhnos Liu |Owner: nobody Type: New feature | Status:

Re: [Django] #30752: Allow using ExceptionReporter subclass in django.views.debug.technical_500_response

#30752: Allow using ExceptionReporter subclass in django.views.debug.technical_500_response -+- Reporter: Carlton Gibson |Owner: Pavel | Lysak Type

Re: [Django] #11919: dpaste.com feature in debug traceback view should be optional

#11919: dpaste.com feature in debug traceback view should be optional -+- Reporter: mike w |Owner: nobody Type: New feature | Status: closed Component: Err

Re: [Django] #27785: Log request.body (or part of it) in the 500 debug content

#27785: Log request.body (or part of it) in the 500 debug content -+- Reporter: Claude Paroz |Owner: (none) Type: New feature | Status: closed Component: Error r

Re: [Django] #25167: Provide option to disable ajax text/plain response in technical_500_response

#25167: Provide option to disable ajax text/plain response in technical_500_response -+- Reporter: thenewguy|Owner: nobody Type: New feature | Status: closed

Re: [Django] #24619: Technical error responses (404 and 500) should return responses dependent on Accept header

#24619: Technical error responses (404 and 500) should return responses dependent on Accept header -+- Reporter: Marcin Nowak |Owner: nobody Type: New feature | Statu

Re: [Django] #28217: nested calls to functions decorated with sensitive_post_parameters produces unexpected results which parameters are considered sensitive

#28217: nested calls to functions decorated with sensitive_post_parameters produces unexpected results which parameters are considered sensitive -+-- Reporter: Peter Zsoldos|Owner: (none) Ty

Re: [Django] #31144: MySQL unique constraints incorrectly limited to 255 char when it should be 1000.

#31144: MySQL unique constraints incorrectly limited to 255 char when it should be 1000. -+- Reporter: Steven Mapes |Owner: nobody Type: Bug | Sta

Re: [Django] #31172: Wrong translation for "yes, no, maybe" in several .po files.

#31172: Wrong translation for "yes,no,maybe" in several .po files. -+- Reporter: José Antonio Ruiz|Owner: José | Antonio Ruiz Type: Bug

Re: [Django] #30190: json lines (jsonl) serializer

#30190: json lines (jsonl) serializer -+- Reporter: aliva|Owner: nobody Type: New feature | Status: closed Component: Core |

[Django] #31173: Testing with PickleSerializer and Mock objects breaks

#31173: Testing with PickleSerializer and Mock objects breaks -+- Reporter: MeNsaaH| Owner: nobody Type: Bug| Status: new Component: Testing|

Re: [Django] #31144: MySQL unique constraints incorrectly limited to 255 char when it should be 1000.

#31144: MySQL unique constraints incorrectly limited to 255 char when it should be 1000. -+- Reporter: Steven Mapes |Owner: nobody Type: Bug | Sta

Re: [Django] #31144: MySQL unique constraints incorrectly limited to 255 char when it should be 1000.

#31144: MySQL unique constraints incorrectly limited to 255 char when it should be 1000. -+- Reporter: Steven Mapes |Owner: nobody Type: Bug | Sta

Re: [Django] #21961: Add support for database-level cascading options

#21961: Add support for database-level cascading options -+- Reporter: Christophe Pettus|Owner: Nick | Stefan Type: New feature |

Re: [Django] #31144: MySQL unique constraints incorrectly limited to 255 char when it should be 1000.

#31144: MySQL unique constraints incorrectly limited to 255 char when it should be 1000. -+- Reporter: Steven Mapes |Owner: nobody Type: Bug | Sta

Re: [Django] #31144: MySQL unique constraints incorrectly limited to 255 char when it should be 1000.

#31144: MySQL unique constraints incorrectly limited to 255 char when it should be 1000. -+- Reporter: Steven Mapes |Owner: nobody Type: Bug | Sta

Re: [Django] #31172: Wrong translation for "yes, no, maybe" in several .po files.

#31172: Wrong translation for "yes,no,maybe" in several .po files. -+- Reporter: José Antonio Ruiz|Owner: José | Antonio Ruiz Type: Bug

Re: [Django] #27785: Log request.body (or part of it) in the 500 debug content

#27785: Log request.body (or part of it) in the 500 debug content -+- Reporter: Claude Paroz |Owner: (none) Type: New feature | Status: closed Component: Error r

Re: [Django] #30439: Translations issues on Django upgrade due to unexpected changes in plural forms

#30439: Translations issues on Django upgrade due to unexpected changes in plural forms --+ Reporter: Michal Čihař |Owner: Rodrigo Type: Bug | S

Re: [Django] #30439: Translations issues on Django upgrade due to unexpected changes in plural forms

#30439: Translations issues on Django upgrade due to unexpected changes in plural forms --+ Reporter: Michal Čihař |Owner: Rodrigo Type: Bug | S

Re: [Django] #29789: Support nested relations in FilteredRelation's condition

#29789: Support nested relations in FilteredRelation's condition -+- Reporter: Thomas Riccardi |Owner: Noumbissi | Valere Gille Geovan Type: New fe

[Django] #31174: The inline original text area can not display full

#31174: The inline original text area can not display full -+- Reporter: daimon99 | Owner: nobody Type: Bug| Status: new Component: Forms |

Re: [Django] #31174: The inline original text area can not display full

#31174: The inline original text area can not display full -+- Reporter: daimon99 |Owner: nobody Type: Bug | Status: new Component: Forms

Re: [Django] #31174: The inline original text area can not display full

#31174: The inline original text area can not display full -+- Reporter: daimon99 |Owner: nobody Type: Bug | Status: new Component: Forms

Re: [Django] #30439: Translations issues on Django upgrade due to unexpected changes in plural forms

#30439: Translations issues on Django upgrade due to unexpected changes in plural forms --+ Reporter: Michal Čihař |Owner: Rodrigo Type: Bug | S

Re: [Django] #31172: Note that yesno can be affected by extra spaces in translations. (was: Wrong translation for "yes, no, maybe" in several .po files.)

#31172: Note that yesno can be affected by extra spaces in translations. -+- Reporter: José Antonio Ruiz|Owner: José | Antonio Ruiz Type: Bug