Re: [Django] #24866: Add CURRENT_TIMESTAMP function to db.functions

#24866: Add CURRENT_TIMESTAMP function to db.functions -+- Reporter: funkybob |Owner: nobody Type: New feature | Status: new Component: Database

Re: [Django] #24866: Add CURRENT_TIMESTAMP function to db.functions

#24866: Add CURRENT_TIMESTAMP function to db.functions -+- Reporter: funkybob |Owner: nobody Type: New feature | Status: new Component: Database

[Django] #24866: Add CURRENT_TIMESTAMP function to db.functions

#24866: Add CURRENT_TIMESTAMP function to db.functions -+- Reporter: funkybob | Owner: nobody Type: New| Status: new feature|

Re: [Django] #24699: Add Avg('DurationField') support on Oracle

#24699: Add Avg('DurationField') support on Oracle -+- Reporter: timgraham|Owner: jarshwah Type: New feature | Status: new Component: Database la

Re: [Django] #24860: Migrations leak stale RelatedManager related_model definitions

#24860: Migrations leak stale RelatedManager related_model definitions -+- Reporter: ecederstrand |Owner: nobody Type: Bug | Status: new Compo

Re: [Django] #24860: Migrations leak stale RelatedManager related_model definitions

#24860: Migrations leak stale RelatedManager related_model definitions -+- Reporter: ecederstrand |Owner: nobody Type: Bug | Status: new Compo

Re: [Django] #24817: Renaming a model field that has null=False makes it nullable in MySQL

#24817: Renaming a model field that has null=False makes it nullable in MySQL -+- Reporter: murfi|Owner: coldmind Type: Bug | Status: assi

Re: [Django] #24853: FK value not inserted in database in data migration

#24853: FK value not inserted in database in data migration -+- Reporter: rakanalh |Owner: nobody Type: Uncategorized| Status: closed Component: D

Re: [Django] #24853: FK value not inserted in database in data migration

#24853: FK value not inserted in database in data migration -+- Reporter: rakanalh |Owner: nobody Type: Uncategorized| Status: new Component: Data

Re: [Django] #24858: Add support for get_foo_display() with ArrayField (was: get_foo_display with the ArrayField)

#24858: Add support for get_foo_display() with ArrayField --+ Reporter: MounirMesselmeni |Owner: Type: New feature | Status: new Component: contrib.postgres |

Re: [Django] #24859: UUIDField does not validate query value (was: UUIDField does not Properly Raise TyperError)

#24859: UUIDField does not validate query value -+- Reporter: cancan101|Owner: nobody Type: | Status: new Cleanup/optimization

Re: [Django] #24859: UUIDField does not Properly Raise TyperError

#24859: UUIDField does not Properly Raise TyperError -+- Reporter: cancan101|Owner: nobody Type: | Status: new Cleanup/optimization

Re: [Django] #24865: Add a feature to programmatically remove stale content types (was: Adding a feature to programmatically remove stale content types)

#24865: Add a feature to programmatically remove stale content types --+ Reporter: Protosac |Owner: nobody Type: New feature | Status: new Compo

[Django] #24865: Adding a feature to programmatically remove stale content types

#24865: Adding a feature to programmatically remove stale content types ---+ Reporter: Protosac | Owner: nobody Type: New feature| Status: new Component: Uncategorized |Version: 1.7 Seve

Re: [Django] #24851: Regression in reverse one-to-one field in list_display

#24851: Regression in reverse one-to-one field in list_display -+- Reporter: jerivas |Owner: timgraham Type: Bug | Status: assigned Component: contr

Re: [Django] #24851: Regression in reverse one-to-one field in list_display

#24851: Regression in reverse one-to-one field in list_display -+- Reporter: jerivas |Owner: timgraham Type: Bug | Status: assigned Component: contr

Re: [Django] #24847: Items set on a RequestContext after creation get lost

#24847: Items set on a RequestContext after creation get lost -+ Reporter: pmdhazy |Owner: pwmarcz Type: Bug | Status: closed Component: Template sy

Re: [Django] #24847: Items set on a RequestContext after creation get lost

#24847: Items set on a RequestContext after creation get lost -+ Reporter: pmdhazy |Owner: pwmarcz Type: Bug | Status: closed Component: Template sy

Re: [Django] #24836: force_text doesn't force SimpleLazyObject into a string

#24836: force_text doesn't force SimpleLazyObject into a string -+- Reporter: riklaunim|Owner: nobody Type: Bug | Status: closed Component

Re: [Django] #12091: Support for WSGI applications within Django (was: [PATCH] Support for WSGI applications within Django)

#12091: Support for WSGI applications within Django ---+ Reporter: Gustavo|Owner: Gustavo Type: New feature| Status: new Component: HTTP handling |

Re: [Django] #24864: Django will not listen to same port on IPv4 and IPv6 at the same time

#24864: Django will not listen to same port on IPv4 and IPv6 at the same time --+-- Reporter: erikano |Owner: nobody Type: New feature | Status: closed Component: Cor

Re: [Django] #21978: Add optional gunicorn support to runserver

#21978: Add optional gunicorn support to runserver -+- Reporter: timo |Owner: | berkerpeksag Type: New feature |

Re: [Django] #24836: force_text doesn't force SimpleLazyObject into a string

#24836: force_text doesn't force SimpleLazyObject into a string -+- Reporter: riklaunim|Owner: nobody Type: Bug | Status: new Component:

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: timo Type: New feature| Status: assigned Componen

Re: [Django] #17914: reverse() does not support namespaced view references

#17914: reverse() does not support namespaced view references -+- Reporter: Bradley Ayers|Owner: nobody | Type: Bug | Status:

Re: [Django] #17914: reverse() does not support namespaced view references

#17914: reverse() does not support namespaced view references -+- Reporter: Bradley Ayers|Owner: nobody | Type: Bug | Status:

Re: [Django] #24864: Django will not listen to same port on IPv4 and IPv6 at the same time

#24864: Django will not listen to same port on IPv4 and IPv6 at the same time ---+-- Reporter: erikano|Owner: nobody Type: Uncategorized | Status: new Component: Unc

Re: [Django] #24616: date_hierarchy with USE_TZ=True won't work with Amazon RDS

#24616: date_hierarchy with USE_TZ=True won't work with Amazon RDS -+- Reporter: iiilx|Owner: nobody Type: | Status: closed Cleanup/

Re: [Django] #24864: Django will not listen to same port on IPv4 and IPv6 at the same time

#24864: Django will not listen to same port on IPv4 and IPv6 at the same time ---+-- Reporter: erikano|Owner: nobody Type: Uncategorized | Status: new Component: Unc

[Django] #24864: Django will not listen to same port on IPv4 and IPv6 at the same time

#24864: Django will not listen to same port on IPv4 and IPv6 at the same time ---+ Reporter: erikano| Owner: nobody Type: Uncategorized | Status: new Component: Uncategorized |Version: 1.8 Severity:

Re: [Django] #24616: date_hierarchy with USE_TZ=True won't work with Amazon RDS

#24616: date_hierarchy with USE_TZ=True won't work with Amazon RDS -+- Reporter: iiilx|Owner: nobody Type: | Status: new Cleanup/opt

[Django] #24863: Make `django.db.models.Manager.from_queryset` copy over properties and not just methods

#24863: Make `django.db.models.Manager.from_queryset` copy over properties and not just methods --+ Reporter: coolRR| Owner: nobody Type: New feature | Status: new

Re: [Django] #24858: get_foo_display with the ArrayField

#24858: get_foo_display with the ArrayField --+-- Reporter: MounirMesselmeni |Owner: Type: Uncategorized | Status: new Component: contrib.postgres |

Re: [Django] #24858: get_foo_display with the ArrayField

#24858: get_foo_display with the ArrayField --+-- Reporter: MounirMesselmeni |Owner: Type: Uncategorized | Status: new Component: contrib.postgres |

Re: [Django] #24862: Patch for GeoDjango to improve error message if database connection is bad

#24862: Patch for GeoDjango to improve error message if database connection is bad -+- Reporter: brycenesbitt |Owner: nobody Type: | Status: