Re: [Django] #1991: User accounts with is_active=False are allowed to login

#1991: User accounts with is_active=False are allowed to login -+-- Reporter: [EMAIL PROTECTED] |Owner: adrian Type: | Status: closed Priority: normal |Milestone

Re: [Django] #1991: User accounts with is_active=False are allowed to login

#1991: User accounts with is_active=False are allowed to login -+-- Reporter: [EMAIL PROTECTED] |Owner: adrian Type: defect | Status: closed Priority: normal |Milestone

Re: [Django] #2467: [patch] date_hierarchy in model is not checked for validity.

#2467: [patch] date_hierarchy in model is not checked for validity. ---+ Reporter: Simon Greenhill, [EMAIL PROTECTED] |Owner: adrian Type: defect | Status: new Priority:

[Django] #2467: [patch] date_hierarchy in model is not checked for validity.

#2467: [patch] date_hierarchy in model is not checked for validity. ---+ Reporter: Simon Greenhill, [EMAIL PROTECTED] | Owner: adrian Type: defect | Status: new Priority:

Re: [Django] #952: [patch] Allow for database client encoding configuration from project settings

#952: [patch] Allow for database client encoding configuration from project settings --+- Reporter: [EMAIL PROTECTED] |Owner: adrian Type:| Status: closed Priority: normal

Re: [Django] #952: [patch] Allow for database client encoding configuration from project settings

#952: [patch] Allow for database client encoding configuration from project settings --+- Reporter: [EMAIL PROTECTED] |Owner: adrian Type: defect| Status: closed Priority: normal

Re: [Django] #952: [patch] Allow for database client encoding configuration from project settings

#952: [patch] Allow for database client encoding configuration from project settings --+- Reporter: [EMAIL PROTECTED] |Owner: adrian Type: defect| Status: closed Priority: normal

Re: [Django] #672: get_absolute_url isn't nice

#672: get_absolute_url isn't nice -+-- Reporter: [EMAIL PROTECTED] |Owner: adrian Type: enhancement | Status: new Priority: low |Milestone: Component: RSS framework

Re: [Django] #648: Add a comment tag like {%# & amp; amp; gt; & amp; amp; gt; commented {{ code }}& amp; amp; lt; & amp; amp; lt; %}

#648: Add a comment tag like {%# >>commented {{ code }}<< %} -+-- Reporter: hegemon |Owner: adrian Type: | Status: closed Priori

Re: [Django] #952: [patch] Allow for database client encoding configuration from project settings

#952: [patch] Allow for database client encoding configuration from project settings --+- Reporter: [EMAIL PROTECTED] |Owner: adrian Type: defect| Status: closed Priority: normal

[Changeset] r3513 - django/branches/multiple-db-support/docs

Author: jpellerin Date: 2006-08-01 17:21:11 -0500 (Tue, 01 Aug 2006) New Revision: 3513 Added: django/branches/multiple-db-support/docs/multiple_database_support.txt Log: [multi-db] Added first, incomplete draft of multiple db doc. Added: django/branches/multiple-db-support/docs/multiple_data

Re: [Django] #2257: [patch] syncdb should generate unique constraint names with hashes

#2257: [patch] syncdb should generate unique constraint names with hashes -+-- Reporter: [EMAIL PROTECTED] |Owner: mtredinnick Type: defect | Status: closed Priority: normal

[Changeset] r3512 - django/trunk/django/core

Author: mtredinnick Date: 2006-08-01 16:46:51 -0500 (Tue, 01 Aug 2006) New Revision: 3512 Modified: django/trunk/django/core/management.py Log: Fixed #2257 -- make constraint names unique across all table/column combinations (for the benefit of MySQL). Modified: django/trunk/django/core/mana

Re: [Django] #2257: [patch] syncdb should generate unique constraint names with hashes

#2257: [patch] syncdb should generate unique constraint names with hashes -+-- Reporter: [EMAIL PROTECTED] |Owner: mtredinnick Type: defect | Status: closed Priority: normal

Re: [Django] #2465: Make select_related() related work for ForeignKeys with null=True

#2465: Make select_related() related work for ForeignKeys with null=True --+- Reporter: Adam Endicott <[EMAIL PROTECTED]> |Owner: jacob Type: enhancement | Status: closed Pri

[Changeset] r3511 - django/trunk/docs

Author: adrian Date: 2006-08-01 16:45:57 -0500 (Tue, 01 Aug 2006) New Revision: 3511 Modified: django/trunk/docs/db-api.txt Log: Fixed #2465 -- Documented the fact that select_related doesn't follow null=True Modified: django/trunk/docs/db-api.txt =

Re: [Django] #2465: Make select_related() related work for ForeignKeys with null=True

#2465: Make select_related() related work for ForeignKeys with null=True --+- Reporter: Adam Endicott <[EMAIL PROTECTED]> |Owner: jacob Type: enhancement | Status: new Prior

Re: [Django] #1796: [patch] "Cannot resolve keyword ___ into field" error when working with ManyToMany relation

#1796: [patch] "Cannot resolve keyword ___ into field" error when working with ManyToMany relation --+- Reporter: anonymous |Owner: mtredinnick Type: defect| Status: closed Prio

Re: [Django] #1796: [patch] "Cannot resolve keyword ___ into field" error when working with ManyToMany relation

#1796: [patch] "Cannot resolve keyword ___ into field" error when working with ManyToMany relation --+- Reporter: anonymous |Owner: mtredinnick Type: defect| Status: reopened Prio

[Changeset] r3510 - django/trunk/django/db/models/fields

Author: mtredinnick Date: 2006-08-01 16:15:41 -0500 (Tue, 01 Aug 2006) New Revision: 3510 Modified: django/trunk/django/db/models/fields/related.py Log: Refs #1796 -- Fixed a problem when creating models with relations to themselves: more than one instance was being created. Modified: django

Re: [Django] #2465: Make select_related() related work for ForeignKeys with null=True

#2465: Make select_related() related work for ForeignKeys with null=True --+- Reporter: Adam Endicott <[EMAIL PROTECTED]> |Owner: jacob Type: enhancement | Status: new Prior

[Changeset] r3509 - django/trunk/docs

Author: adrian Date: 2006-08-01 15:48:26 -0500 (Tue, 01 Aug 2006) New Revision: 3509 Modified: django/trunk/docs/add_ons.txt Log: Added link to 'batteries included' explanation in docs/add_ons.txt Modified: django/trunk/docs/add_ons.txt

Re: [Django] #2417: Support for binary type fields (aka: bytea in postgres and VARBINARY in mysql)

#2417: Support for binary type fields (aka: bytea in postgres and VARBINARY in mysql) -+-- Reporter: [EMAIL PROTECTED] |Owner: jacob Type: enhancement | Status: assigned Priority: normal

Re: [Django] #2466: [patch] Add a 'filesize' filter to the 'humanize' template tags

#2466: [patch] Add a 'filesize' filter to the 'humanize' template tags --+- Reporter: [EMAIL PROTECTED] |Owner: adrian Type: enhancement | Status: closed Priority: normal|Miles

Re: [Django] #1796: [patch] "Cannot resolve keyword ___ into field" error when working with ManyToMany relation

#1796: [patch] "Cannot resolve keyword ___ into field" error when working with ManyToMany relation --+- Reporter: anonymous |Owner: mtredinnick Type: defect| Status: reopened Prio

Re: [Django] #2365: [patch] models.FloatField should be renamed

#2365: [patch] models.FloatField should be renamed ---+ Reporter: [EMAIL PROTECTED] |Owner: adrian Type: defect | Status: new Priority: normal |Milestone: Compon

[Django] #2466: [patch] Add a 'filesize' filter to the 'humanize' template tags

#2466: [patch] Add a 'filesize' filter to the 'humanize' template tags --+- Reporter: [EMAIL PROTECTED] | Owner: adrian Type: enhancement | Status: new Priority: normal| Milestone:

Re: [Django] #1796: [patch] "Cannot resolve keyword ___ into field" error when working with ManyToMany relation

#1796: [patch] "Cannot resolve keyword ___ into field" error when working with ManyToMany relation --+- Reporter: anonymous |Owner: mtredinnick Type: defect| Status: reopened Prio

Re: [Django] #1796: [patch] "Cannot resolve keyword ___ into field" error when working with ManyToMany relation

#1796: [patch] "Cannot resolve keyword ___ into field" error when working with ManyToMany relation --+- Reporter: anonymous |Owner: mtredinnick Type: defect| Status: reopened Prio

Re: [Django] #2417: Support for binary type fields (aka: bytea in postgres and VARBINARY in mysql)

#2417: Support for binary type fields (aka: bytea in postgres and VARBINARY in mysql) -+-- Reporter: [EMAIL PROTECTED] |Owner: jacob Type: enhancement | Status: assigned Priority: normal

[Django] #2465: [patch] doc addition - select_related() and null=True

#2465: [patch] doc addition - select_related() and null=True --+- Reporter: Adam Endicott <[EMAIL PROTECTED]> | Owner: jacob Type: enhancement | Status: new Priority: normal

Re: [Django] #851: kakalu.com

#851: kakalu.com --+- Reporter: aaronsw |Owner: adrian Type: enhancement | Status: closed Priority: normal|Milestone: Component: Database wrapper | Ver

Re: [Django] #526: Error when edit_inline model have unique_together constraint

#526: Error when edit_inline model have unique_together constraint --+- Reporter: nesh |Owner: adrian Type: defect| Status: new Priority: high

Re: [Django] #526: Exception when using unique_together in edit_inline model

#526: Exception when using unique_together in edit_inline model --+- Reporter: nesh |Owner: adrian Type: defect| Status: new Priority: high

Re: [Django] #526: Exception when using unique_together in edit_inline model

#526: Exception when using unique_together in edit_inline model --+- Reporter: nesh |Owner: adrian Type: defect| Status: new Priority: high

Re: [Django] #2464: Tiny mistake in "Formfields and manipulators" doc (I guess)

#2464: Tiny mistake in "Formfields and manipulators" doc (I guess) ---+ Reporter: konryd |Owner: jacob Type: defect | Status: closed Priority: low|Milestone:

Re: [Django] #526: Exception when using unique_together in edit_inline model

#526: Exception when using unique_together in edit_inline model --+- Reporter: nesh |Owner: adrian Type: defect| Status: new Priority: high

[Django] #2464: Tiny mistake in "Formfields and manipulators" doc (I guess)

#2464: Tiny mistake in "Formfields and manipulators" doc (I guess) ---+ Reporter: konryd | Owner: jacob Type: defect | Status: new Priority: low| Milestone: Componen

Re: [Django] #2463: [patch] "'ManyToManyRel' object has no attribute 'get_related_field'" error appears for all forms with M2M fields

#2463: [patch] "'ManyToManyRel' object has no attribute 'get_related_field'" error appears for all forms with M2M fields +--- Reporter: [EMAIL PROTECTED] |Owner: adrian Type: defect | Statu

[Changeset] r3508 - django/trunk/django/db/models/fields

Author: adrian Date: 2006-08-01 09:20:01 -0500 (Tue, 01 Aug 2006) New Revision: 3508 Modified: django/trunk/django/db/models/fields/__init__.py Log: Fixed #2463 -- Fixed temporarily broken many-to-many fields in admin interface due to [3507]. Thanks, Nesh Modified: django/trunk/django/db/mod

Re: [Django] #2365: [patch] models.FloatField should be renamed

#2365: [patch] models.FloatField should be renamed ---+ Reporter: [EMAIL PROTECTED] |Owner: adrian Type: defect | Status: new Priority: normal |Milestone: Compon

Re: [Django] #2366: [patch] forms.FloatField is incompatible with models.FloatField

#2366: [patch] forms.FloatField is incompatible with models.FloatField ---+ Reporter: [EMAIL PROTECTED] |Owner: adrian Type: defect | Status: closed Priority: normal |

Re: [Django] #2450: [patch] add ascending sort option to date_based generic views

#2450: [patch] add ascending sort option to date_based generic views ---+ Reporter: noods |Owner: jacob Type: enhancement| Status: new Priority: normal |Milestone: Com

Re: [Django] #2070: [patch] Large streaming uploads

#2070: [patch] Large streaming uploads --+- Reporter: [EMAIL PROTECTED] |Owner: jacob Type: enhancement | Status: assigned Priority: normal|Milestone:

Re: [Django] #2463: [patch] "'ManyToManyRel' object has no attribute 'get_related_field'" error appears for all forms with M2M fields

#2463: [patch] "'ManyToManyRel' object has no attribute 'get_related_field'" error appears for all forms with M2M fields +--- Reporter: [EMAIL PROTECTED] |Owner: adrian Type: defect | Statu

Re: [Django] #2463: "'ManyToManyRel' object has no attribute 'get_related_field'" error appears for all forms with M2M fields

#2463: "'ManyToManyRel' object has no attribute 'get_related_field'" error appears for all forms with M2M fields +--- Reporter: [EMAIL PROTECTED] |Owner: adrian Type: defect | Status: new

Re: [Django] #952: [patch] Allow for database client encoding configuration from project settings

#952: [patch] Allow for database client encoding configuration from project settings --+- Reporter: [EMAIL PROTECTED] |Owner: adrian Type:| Status: closed Priority: normal

[Django] #2463: "'ManyToManyRel' object has no attribute 'get_related_field'" error appears for all forms with M2M fields

#2463: "'ManyToManyRel' object has no attribute 'get_related_field'" error appears for all forms with M2M fields +--- Reporter: [EMAIL PROTECTED] | Owner: adrian Type: defect | Status: new

Re: [Django] #1030: auto_now_add is broken for inline edited field

#1030: auto_now_add is broken for inline edited field --+- Reporter: titoo |Owner: adrian Type: defect| Status: new Priority: high |Milestone: Compon

Re: [Django] #2243: [patch] admin tries to set M2M inside a reverse foreign key

#2243: [patch] admin tries to set M2M inside a reverse foreign key --+- Reporter: [EMAIL PROTECTED] |Owner: adrian Type: defect| Status: new Priority: high |Milestone:

Re: [Django] #2454: [patch] for-loops reset state of inner ifchanged

#2454: [patch] for-loops reset state of inner ifchanged +--- Reporter: [EMAIL PROTECTED] |Owner: adrian Type: enhancement | Status: new Priority: normal |Milestone:

[Django] #2462: Related Object Lookup Popup Window is too small

#2462: Related Object Lookup Popup Window is too small ---+ Reporter: [EMAIL PROTECTED] | Owner: adrian Type: defect | Status: new Priority: normal | Mileston