Re: [Django] #26500: Implement select_for_update(skip_locked=True) for Postgresql and Oracle

#26500: Implement select_for_update(skip_locked=True) for Postgresql and Oracle -+- Reporter: charettes|Owner: nobody Type: New feature | Status: new

Re: [Django] #9025: Nested Inline Support in Admin

#9025: Nested Inline Support in Admin ---+ Reporter: pixelcort |Owner: auvipy Type: New feature| Status: assigned Component: contrib.admin | Versio

Re: [Django] #5863: list_display does not allow functions of referenced objects

#5863: list_display does not allow functions of referenced objects -+- Reporter: Beat Bolli |Owner: nobody | Type: Uncategorized|

Re: [Django] #10743: Support lookup separators in ModelAdmin.list_display

#10743: Support lookup separators in ModelAdmin.list_display -+- Reporter: mrts |Owner: nobody Type: New feature | Status: new Component: con

[Django] #26500: Implement select_for_update(skip_locked=True) for Postgresql and Oracle

#26500: Implement select_for_update(skip_locked=True) for Postgresql and Oracle -+- Reporter: charettes | Owner: nobody Type: New| Status: new feature

Re: [Django] #26499: AuthenticationMiddleware apparently accesses request.POST

#26499: AuthenticationMiddleware apparently accesses request.POST -+- Reporter: ChristopherBrix |Owner: nobody Type: Bug | Status: closed Compone

Re: [Django] #26499: AuthenticationMiddleware apparently accesses request.POST

#26499: AuthenticationMiddleware apparently accesses request.POST -+- Reporter: ChristopherBrix |Owner: nobody Type: Bug | Status: new Component:

[Django] #26499: AuthenticationMiddleware apparently accesses request.POST

#26499: AuthenticationMiddleware apparently accesses request.POST -+- Reporter: ChristopherBrix | Owner: nobody Type: Bug | Status: new Component: Uncategorized|Version: 1.9

Re: [Django] #26497: No Capitalization of user-defined verbose_names of model fields

#26497: No Capitalization of user-defined verbose_names of model fields -+-- Reporter: srkunze |Owner: nobody Type: New feature | Status: closed Component: Forms

Re: [Django] #26484: Add a helpful message in manage.py when Django cannot be imported

#26484: Add a helpful message in manage.py when Django cannot be imported --+ Reporter: timgraham |Owner: nobody Type: Cleanup/optimization | Status: closed

Re: [Django] #26005: uri_to_iri() perfoms percent decoding incorrectly

#26005: uri_to_iri() perfoms percent decoding incorrectly ---+--- Reporter: Chronial |Owner: varunnaganathan Type: Bug| Status: assigned Component: Utilities |

Re: [Django] #26484: Add a helpful message in manage.py when Django cannot be imported

#26484: Add a helpful message in manage.py when Django cannot be imported --+ Reporter: timgraham |Owner: nobody Type: Cleanup/optimization | Status: new

Re: [Django] #26484: Add a helpful message in manage.py when Django cannot be imported

#26484: Add a helpful message in manage.py when Django cannot be imported --+ Reporter: timgraham |Owner: nobody Type: Cleanup/optimization | Status: new

Re: [Django] #26497: No Capitalization of user-defined verbose_names of model fields

#26497: No Capitalization of user-defined verbose_names of model fields -+-- Reporter: srkunze |Owner: nobody Type: New feature | Status: closed Component: Forms

Re: [Django] #26497: No Capitalization of user-defined verbose_names of model fields

#26497: No Capitalization of user-defined verbose_names of model fields -+-- Reporter: srkunze |Owner: nobody Type: New feature | Status: closed Component: Forms

Re: [Django] #26497: No Capitalization of user-defined verbose_names of model fields (was: No Capitalization of verbose_name of model fields when Rendered by BoundField)

#26497: No Capitalization of user-defined verbose_names of model fields -+-- Reporter: srkunze |Owner: nobody Type: New feature | Status: closed Component: Forms

Re: [Django] #26497: No Capitalization of verbose_name of model fields when Rendered by BoundField

#26497: No Capitalization of verbose_name of model fields when Rendered by BoundField -+-- Reporter: srkunze |Owner: nobody Type: New feature | Status: closed Component:

Re: [Django] #26497: No Capitalization of verbose_name of model fields when Rendered by BoundField

#26497: No Capitalization of verbose_name of model fields when Rendered by BoundField -+-- Reporter: srkunze |Owner: nobody Type: New feature | Status: closed Component:

Re: [Django] #26498: Data loss of microseconds on MySQL and SQLite

#26498: Data loss of microseconds on MySQL and SQLite -+- Reporter: adamchainz |Owner: nobody Type: Bug | Status: new Component: Database l

Re: [Django] #26498: Data loss of microseconds on MySQL and SQLite

#26498: Data loss of microseconds on MySQL and SQLite -+- Reporter: adamchainz |Owner: nobody Type: Bug | Status: new Component: Database l

Re: [Django] #26497: No Capitalization of verbose_name of model fields when Rendered by BoundField

#26497: No Capitalization of verbose_name of model fields when Rendered by BoundField -+-- Reporter: srkunze |Owner: nobody Type: New feature | Status: closed Component:

Re: [Django] #26498: Data loss of microseconds on MySQL and SQLite

#26498: Data loss of microseconds on MySQL and SQLite -+- Reporter: adamchainz |Owner: nobody Type: Bug | Status: new Component: Database l

Re: [Django] #26498: Data loss of microseconds on MySQL and SQLite

#26498: Data loss of microseconds on MySQL and SQLite -+- Reporter: adamchainz |Owner: nobody Type: Bug | Status: new Component: Database l

Re: [Django] #26498: Data loss of microseconds on MySQL and SQLite

#26498: Data loss of microseconds on MySQL and SQLite -+- Reporter: adamchainz |Owner: nobody Type: Bug | Status: new Component: Database l

Re: [Django] #26498: Data loss of microseconds on MySQL and SQLite

#26498: Data loss of microseconds on MySQL and SQLite -+- Reporter: adamchainz |Owner: nobody Type: Bug | Status: new Component: Database l

Re: [Django] #26498: Data loss of microseconds on MySQL and SQLite

#26498: Data loss of microseconds on MySQL and SQLite -+- Reporter: adamchainz |Owner: nobody Type: Uncategorized| Status: new Component: Database l

[Django] #26498: Data loss of microseconds on MySQL and SQLite

#26498: Data loss of microseconds on MySQL and SQLite --+ Reporter: adamchainz| Owner: nobody Type: Uncategorized | Status: new Component: Database layer (models, ORM)

Re: [Django] #22383: Add the required tag to the input fields which are required for database entry

#22383: Add the required tag to the input fields which are required for database entry -+ Reporter: abhishek.garg@… |Owner: Type: New feature | Status: new Component:

Re: [Django] #26497: No Capitalization of verbose_name of model fields when Rendered by BoundField

#26497: No Capitalization of verbose_name of model fields when Rendered by BoundField -+-- Reporter: srkunze |Owner: nobody Type: New feature | Status: closed Component:

Re: [Django] #26486: Fix select_related() + defer() MTI tests marked as @expectedFailure

#26486: Fix select_related() + defer() MTI tests marked as @expectedFailure -+- Reporter: timgraham|Owner: timgraham Type: Bug | Status: close

Re: [Django] #16508: Provide real support for virtual fields

#16508: Provide real support for virtual fields -+- Reporter: vzima|Owner: pirosb3 Type: New feature | Status: assigned Component: Database l

Re: [Django] #26486: Fix select_related() + defer() MTI tests marked as @expectedFailure

#26486: Fix select_related() + defer() MTI tests marked as @expectedFailure -+- Reporter: timgraham|Owner: timgraham Type: Bug | Status: assig

Re: [Django] #26497: No Capitalization of verbose_name of model fields when Rendered by BoundField

#26497: No Capitalization of verbose_name of model fields when Rendered by BoundField -+-- Reporter: srkunze |Owner: nobody Type: New feature | Status: closed Component:

Re: [Django] #26497: No Capitalization of verbose_name of model fields when Rendered by BoundField

#26497: No Capitalization of verbose_name of model fields when Rendered by BoundField -+-- Reporter: srkunze |Owner: nobody Type: New feature | Status: closed Component:

Re: [Django] #26497: No Capitalization of verbose_name of model fields when Rendered by BoundField

#26497: No Capitalization of verbose_name of model fields when Rendered by BoundField -+-- Reporter: srkunze |Owner: nobody Type: New feature | Status: closed Component:

Re: [Django] #26497: No Capitalization of verbose_name of model fields when Rendered by BoundField

#26497: No Capitalization of verbose_name of model fields when Rendered by BoundField ---+-- Reporter: srkunze|Owner: nobody Type: Uncategorized | Status: closed Comp

Re: [Django] #21231: Limiting the number of variables and files that a POST request can contain

#21231: Limiting the number of variables and files that a POST request can contain ---+ Reporter: epandurski@… |Owner: Type: New feature| Status: new Component: HTTP ha

Re: [Django] #26493: Document that built-in signals use send()

#26493: Document that built-in signals use send() -+- Reporter: marfire |Owner: filias Type: | Status: closed Cleanup/optimization

Re: [Django] #26493: Document that built-in signals use send()

#26493: Document that built-in signals use send() -+- Reporter: marfire |Owner: filias Type: | Status: closed Cleanup/optimization

Re: [Django] #26493: Document that built-in signals use send()

#26493: Document that built-in signals use send() -+- Reporter: marfire |Owner: filias Type: | Status: assigned Cleanup/optimization

Re: [Django] #24787: Cannot assign a ForeignKey field with blank=True and null=False in Model.clean()

#24787: Cannot assign a ForeignKey field with blank=True and null=False in Model.clean() -+ Reporter: mssnlayam|Owner: nobody Type: New feature | Status: closed Component

Re: [Django] #26496: AdminEmailHandler can produce mails violating RFC2822

#26496: AdminEmailHandler can produce mails violating RFC2822 -+ Reporter: nijel|Owner: Type: Bug | Status: new Component: Error reporting |

[Django] #26497: No Capitalization of verbose_name of model fields when Rendered by BoundField

#26497: No Capitalization of verbose_name of model fields when Rendered by BoundField ---+ Reporter: srkunze| Owner: nobody Type: Uncategorized | Status: new Component: Forms |Version: 1.8 Se

Re: [Django] #22561: EmailMessage should respect RFC2822 on max line length

#22561: EmailMessage should respect RFC2822 on max line length -+- Reporter: notsqrt |Owner: levkowetz Type: Bug | Status: assigned Component: Core (Mail) |

[Django] #26496: AdminEmailHandler can produce mails violating RFC2822

#26496: AdminEmailHandler can produce mails violating RFC2822 -+- Reporter: nijel| Owner: Type: Bug | Status: new Component: Error reporting |Version: 1.9 Severity: Normal |

Re: [Django] #26493: Document that built-in signals use send()

#26493: Document that built-in signals use send() --+ Reporter: marfire |Owner: filias Type: Cleanup/optimization | Status: assigned Component: Documen

Re: [Django] #26493: Document that built-in signals use send()

#26493: Document that built-in signals use send() --+ Reporter: marfire |Owner: filias Type: Cleanup/optimization | Status: assigned Component: Documen