Re: [Django] #10476: Fix(?) model insert handling when autcommit=True for PostgreSQL <= 8.1

#10476: Fix(?) model insert handling when autcommit=True for PostgreSQL <= 8.1 ---+ Reporter: mtredinnick | Owner: mtredinnick Status: new |

[Django] #10476: Fix(?) model insert handling when autcommit=True for PostgreSQL <= 8.1

#10476: Fix(?) model insert handling when autcommit=True for PostgreSQL <= 8.1 --+- Reporter: mtredinnick | Owner: mtredinnick Status: new | Milestone: 1.1 beta

Re: [Django] #10469: New postgres autocommit references global DATABASE_OPTIONS instead of it's connection's

#10469: New postgres autocommit references global DATABASE_OPTIONS instead of it's connection's ---+ Reporter: Alex | Owner: Alex Status: closed

[Changeset] r10035 - django/trunk/django/db/backends/postgresql_psycopg2

Author: mtredinnick Date: 2009-03-12 00:32:00 -0500 (Thu, 12 Mar 2009) New Revision: 10035 Modified: django/trunk/django/db/backends/postgresql_psycopg2/base.py Log: Fixed #10467 -- Fixed generated INSERT SQL for PostgreSQL 8.1 and earlier. I introduced a bad regression in r10029, forgetting

[Changeset] r10034 - django/trunk/django/db/models/sql

Author: mtredinnick Date: 2009-03-12 00:31:34 -0500 (Thu, 12 Mar 2009) New Revision: 10034 Modified: django/trunk/django/db/models/sql/subqueries.py Log: Return last insert ID correctly when the feature is enabled. This was overlooked when merging the patch from #3460 in r10029. Thank to Ian

Re: [Django] #10469: New postgres autocommit references global DATABASE_OPTIONS instead of it's connection's

#10469: New postgres autocommit references global DATABASE_OPTIONS instead of it's connection's ---+ Reporter: Alex | Owner: Alex Status: closed

[Changeset] r10033 - django/trunk/django/db/backends/postgresql_psycopg2

Author: mtredinnick Date: 2009-03-12 00:30:51 -0500 (Thu, 12 Mar 2009) New Revision: 10033 Modified: django/trunk/django/db/backends/postgresql_psycopg2/base.py Log: Slight refactoring of isolation setting from r10029. There was a bug in the way we were reading the DATABASE_OPTIONS setting

Re: [Django] #7596: Multiple Database Inserts using 1 query

#7596: Multiple Database Inserts using 1 query ---+ Reporter: erikcw| Owner: nobody Status: new | Milestone:

Re: [Django] #10469: New postgres autocommit references global DATABASE_OPTIONS instead of it's connection's

#10469: New postgres autocommit references global DATABASE_OPTIONS instead of it's connection's ---+ Reporter: Alex | Owner: Alex Status: new

Re: [Django] #9230: Iterating over checkboxes in CheckboxSelectMultiple should be possible

#9230: Iterating over checkboxes in CheckboxSelectMultiple should be possible --+- Reporter: mtredinnick | Owner: mtredinnick Status: new | Milestone:

Re: [Django] #9596: Comparing a DateTimeField to a date is too hard

#9596: Comparing a DateTimeField to a date is too hard ---+ Reporter: dja...@mashi.org | Owner: nobody Status:

Re: [Django] #10475: PDF documentation does not build...

#10475: PDF documentation does not build... +--- Reporter: yacoob | Owner: nobody Status: closed | Milestone: Component: Documentation | Version:

[Django] #10475: PDF documentation does not build...

#10475: PDF documentation does not build... ---+ Reporter: yacoob | Owner: nobody Status: new| Milestone: Component: Documentation | Version: 1.0 Keywords:

Re: [Django] #10474: Changeset 10029 - syntax error at or near "RETURNING" at character 211

#10474: Changeset 10029 - syntax error at or near "RETURNING" at character 211 -+-- Reporter: aeby| Owner: mtredinnick Status: closed | Milestone:

Re: [Django] #10474: Changeset 10029 - syntax error at or near "RETURNING" at character 211

#10474: Changeset 10029 - syntax error at or near "RETURNING" at character 211 -+-- Reporter: aeby| Owner: mtredinnick Status: new | Milestone:

[Django] #10474: Changeset 10029 - syntax error at or near "RETURNING" at character 211

#10474: Changeset 10029 - syntax error at or near "RETURNING" at character 211 +--- Reporter: aeby| Owner: mtredinnick Status: new | Milestone: Component: Core framework |

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

#10134: unique_for_* broken? ---+ Reporter: wdoekes | Owner: nobody Status: new | Milestone: 1.1

Re: [Django] #10471: django.contrib.admin fails on big tables with foreign keys in list_display

#10471: django.contrib.admin fails on big tables with foreign keys in list_display --+- Reporter: arutdag (a) mail dot ru | Owner: nobody Status: closed

Re: [Django] #10471: django.contrib.admin fails on big tables with foreign keys in list_display

#10471: django.contrib.admin fails on big tables with foreign keys in list_display --+- Reporter: arutdag (a) mail dot ru | Owner: nobody Status: closed

Re: [Django] #9554: admin app's change list usage of select related - maximum depth

#9554: admin app's change list usage of select related - maximum depth ---+ Reporter: gert | Owner: nobody Status: closed|

Re: [Django] #10473: Add support for "RETURNING" to Oracle backend.

#10473: Add support for "RETURNING" to Oracle backend. ---+ Reporter: ikelly| Owner: nobody Status: new | Milestone: 1.1 beta

[Django] #10473: Add support for "RETURNING" to Oracle backend.

#10473: Add support for "RETURNING" to Oracle backend. --+- Reporter: ikelly| Owner: nobody Status: new | Milestone: 1.1 Component: Database layer

Re: [Django] #10467: Remove use of "RETURNING" in PostgreSQL backends by default

#10467: Remove use of "RETURNING" in PostgreSQL backends by default ---+ Reporter: mtredinnick | Owner: mtredinnick Status: new | Milestone: 1.1

[Changeset] r10032 - django/trunk/django/db/backends/oracle

Author: ikelly Date: 2009-03-11 16:14:18 -0500 (Wed, 11 Mar 2009) New Revision: 10032 Modified: django/trunk/django/db/backends/oracle/creation.py Log: Fixed some breakages in the Oracle test database handling from r10026. Modified: django/trunk/django/db/backends/oracle/creation.py

Re: [Django] #10470: Core handlers are not threadsafe

#10470: Core handlers are not threadsafe -+-- Reporter: tdterry | Owner: tdterry Status: assigned| Milestone:

Re: [Django] #10470: Core handlers are not threadsafe

#10470: Core handlers are not threadsafe -+-- Reporter: tdterry | Owner: tdterry Status: assigned| Milestone:

Re: [Django] #10470: Core handlers are not threadsafe

#10470: Core handlers are not threadsafe -+-- Reporter: tdterry | Owner: tdterry Status: assigned| Milestone:

Re: [Django] #10470: Core handlers are not threadsafe

#10470: Core handlers are not threadsafe -+-- Reporter: tdterry | Owner: tdterry Status: assigned| Milestone:

Re: [Django] #10470: Core handlers are not threadsafe

#10470: Core handlers are not threadsafe -+-- Reporter: tdterry | Owner: tdterry Status: assigned| Milestone:

Re: [Django] #10470: Core handlers are not threadsafe

#10470: Core handlers are not threadsafe -+-- Reporter: tdterry | Owner: tdterry Status: assigned| Milestone:

Re: [Django] #10470: Core handlers are not threadsafe

#10470: Core handlers are not threadsafe -+-- Reporter: tdterry | Owner: tdterry Status: assigned| Milestone:

Re: [Django] #10470: Core handlers are not threadsafe

#10470: Core handlers are not threadsafe -+-- Reporter: tdterry | Owner: tdterry Status: assigned| Milestone:

Re: [Django] #10456: Canada localflavor improvements/fixes

#10456: Canada localflavor improvements/fixes -+-- Reporter: mmulley | Owner: nobody Status: new | Milestone:

Re: [Django] #10456: Canada localflavor improvements/fixes

#10456: Canada localflavor improvements/fixes -+-- Reporter: mmulley | Owner: nobody Status: new | Milestone:

Re: [Django] #10470: Core handlers are not threadsafe

#10470: Core handlers are not threadsafe -+-- Reporter: tdterry | Owner: tdterry Status: assigned| Milestone:

Re: [Django] #10470: Core handlers are not threadsafe

#10470: Core handlers are not threadsafe -+-- Reporter: tdterry | Owner: tdterry Status: assigned| Milestone:

Re: [Django] #10472: RegexURLResolver.reverse() is not threadsafe

#10472: RegexURLResolver.reverse() is not threadsafe -+-- Reporter: tdterry | Owner: tdterry Status: assigned| Milestone:

Re: [Django] #10472: RegexURLResolver.reverse() is not threadsafe

#10472: RegexURLResolver.reverse() is not threadsafe -+-- Reporter: tdterry | Owner: tdterry Status: assigned| Milestone:

Re: [Django] #10456: Canada localflavor improvements/fixes

#10456: Canada localflavor improvements/fixes -+-- Reporter: mmulley | Owner: nobody Status: new | Milestone:

Re: [Django] #10470: Core handlers are not threadsafe

#10470: Core handlers are not threadsafe -+-- Reporter: tdterry | Owner: tdterry Status: assigned| Milestone:

Re: [Django] #10470: Core handlers are not threadsafe

#10470: Core handlers are not threadsafe -+-- Reporter: tdterry | Owner: tdterry Status: assigned| Milestone:

Re: [Django] #10472: RegexURLResolver.reverse() is not threadsafe

#10472: RegexURLResolver.reverse() is not threadsafe -+-- Reporter: tdterry | Owner: tdterry Status: assigned| Milestone:

Re: [Django] #10470: Core handlers are not threadsafe

#10470: Core handlers are not threadsafe -+-- Reporter: tdterry | Owner: tdterry Status: assigned| Milestone:

Re: [Django] #10468: django/db/models/sql/query.py fails on tuple unpacking

#10468: django/db/models/sql/query.py fails on tuple unpacking -+-- Reporter: anonymous | Owner: nobody Status: closed | Milestone:

Re: [Django] #10454: IntegrityError while deleting object with complex constraint

#10454: IntegrityError while deleting object with complex constraint ---+ Reporter: liangent | Owner: nobody Status: new | Milestone:

Re: [Django] #10470: Core handlers are not threadsafe

#10470: Core handlers are not threadsafe -+-- Reporter: tdterry | Owner: tdterry Status: assigned| Milestone:

Re: [Django] #10472: RegexURLResolver.reverse() is not threadsafe

#10472: RegexURLResolver.reverse() is not threadsafe +--- Reporter: tdterry| Owner: tdterry Status: assigned | Milestone:

[Django] #10472: RegexURLResolver.reverse() is not threadsafe

#10472: RegexURLResolver.reverse() is not threadsafe ---+ Reporter: tdterry| Owner: nobody Status: new| Milestone: Component:

[Django] #10471: django.contrib.admin fails on big tables with foreign keys in list_display

#10471: django.contrib.admin fails on big tables with foreign keys in list_display --+- Reporter: arutdag (a) mail dot ru | Owner: nobody Status: new |

Re: [Django] #10470: Core handlers are not threadsafe

#10470: Core handlers are not threadsafe -+-- Reporter: tdterry | Owner: nobody Status: new | Milestone:

[Django] #10470: Core handlers are not threadsafe

#10470: Core handlers are not threadsafe ---+ Reporter: tdterry| Owner: nobody Status: new| Milestone: Component:

[Django] #10469: New postgres autocommit references global DATABASE_OPTIONS instead of it's connection's

#10469: New postgres autocommit references global DATABASE_OPTIONS instead of it's connection's --+- Reporter: Alex | Owner: nobody Status: new |

Re: [Django] #10468: django/db/models/sql/query.py fails on tuple unpacking

#10468: django/db/models/sql/query.py fails on tuple unpacking -+-- Reporter: anonymous | Owner: nobody Status: closed | Milestone:

Re: [Django] #10468: django/db/models/sql/query.py fails on tuple unpacking

#10468: django/db/models/sql/query.py fails on tuple unpacking -+-- Reporter: anonymous | Owner: nobody Status: new | Milestone:

[Django] #10468: django/db/models/sql/query.py fails on tuple unpacking

#10468: django/db/models/sql/query.py fails on tuple unpacking -+-- Reporter: anonymous| Owner: nobody Status: new | Milestone: Component: Core framework | Version:

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 Status: reopened| Milestone: Component: Core framework |

Re: [Django] #9362: InlineAdminForm breaks content_type FK on model

#9362: InlineAdminForm breaks content_type FK on model ---+ Reporter: carljm| Owner: brosner Status: assigned | Milestone: Component:

Re: [Django] #10365: localflavor.ca.ca_provinces incorrect.

#10365: localflavor.ca.ca_provinces incorrect. -+-- Reporter: bartek | Owner: nobody Status: new | Milestone: 1.1 Component:

Re: [Django] #10456: Canada localflavor improvements/fixes

#10456: Canada localflavor improvements/fixes -+-- Reporter: mmulley | Owner: nobody Status: new | Milestone:

[Django] #10467: Remove use of "RETURNING" in PostgreSQL backends by default

#10467: Remove use of "RETURNING" in PostgreSQL backends by default --+- Reporter: mtredinnick | Owner: mtredinnick Status: new | Milestone: 1.1 beta Component:

[Changeset] r10031 - in django/trunk: django/core/cache/backends docs/internals docs/topics tests/regressiontests/cache

Author: russellm Date: 2009-03-11 08:27:03 -0500 (Wed, 11 Mar 2009) New Revision: 10031 Modified: django/trunk/django/core/cache/backends/base.py django/trunk/django/core/cache/backends/db.py django/trunk/django/core/cache/backends/memcached.py

[Django] #10466: functions as QuerySets' parameters are not lazy

#10466: functions as QuerySets' parameters are not lazy --+- Reporter: liangent | Owner: nobody Status: new | Milestone: Component: Database layer

Re: [Django] #10465: Reports is broken in oracle

#10465: Reports is broken in oracle +--- Reporter: palcubilla | Owner: nobody Status: closed | Milestone: Component: Uncategorized |

Re: [Django] #7258: connection in WhereNode does not come down from Query

#7258: connection in WhereNode does not come down from Query ---+ Reporter: Koen Biermans | Owner: nobody Status: reopened

Re: [Django] #10449: Bug: HTML accents not escaped out when using newforms

#10449: Bug: HTML accents not escaped out when using newforms ---+ Reporter: tipan | Owner: nobody Status: reopened | Milestone:

[Changeset] r10030 - django/trunk/django/db/backends/mysql

Author: russellm Date: 2009-03-11 06:03:36 -0500 (Wed, 11 Mar 2009) New Revision: 10030 Modified: django/trunk/django/db/backends/mysql/base.py Log: Fixed #10463 -- Corrected a problem with the MySQL backend, introduced by [10026]. Modified: django/trunk/django/db/backends/mysql/base.py

Re: [Django] #9282: Inclusion of comment-utils moderator facility

#9282: Inclusion of comment-utils moderator facility --+- Reporter: thejaswi_puthraya| Owner: jezdez Status: assigned | Milestone:

Re: [Django] #10462: Problem: 10025/10026 - TIME_ZONE

#10462: Problem: 10025/10026 - TIME_ZONE -+-- Reporter: hans.ra...@gmx.net | Owner: nobody Status: closed | Milestone: 1.1 beta Component: Uncategorized |

[Django] #10465: Reports is broken in oracle

#10465: Reports is broken in oracle +--- Reporter: palcubilla | Owner: nobody Status: new | Milestone: Component: Uncategorized | Version: SVN Keywords: reports

Re: [Django] #10463: Could not initialize mysql backend since revision #10026

#10463: Could not initialize mysql backend since revision #10026 ---+ Reporter: aprilmay | Owner: nobody Status: new | Milestone:

Re: [Django] #10462: Problem: 10025/10026 - TIME_ZONE

#10462: Problem: 10025/10026 - TIME_ZONE -+-- Reporter: hans.ra...@gmx.net | Owner: nobody Status: new | Milestone: 1.1 beta Component: Uncategorized |

[Django] #10464: Django Lighttpd Deployment Addition

#10464: Django Lighttpd Deployment Addition ---+ Reporter: dgt84 | Owner: nobody Status: new| Milestone: Component: Documentation | Version: 1.0 Keywords:

Re: [Django] #10463: Could not initialize mysql backend since revision #10026

#10463: Could not initialize mysql backend since revision #10026 ---+ Reporter: aprilmay | Owner: nobody Status: new | Milestone:

[Django] #10463: Could not initialize mysql backend since revision #10026

#10463: Could not initialize mysql backend since revision #10026 --+- Reporter: aprilmay | Owner: nobody Status: new | Milestone: Component:

[Django] #10462: Problem: 10025/10026 - TIME_ZONE

#10462: Problem: 10025/10026 - TIME_ZONE +--- Reporter: hans.ra...@gmx.net | Owner: nobody Status: new | Milestone: 1.1 beta Component: Uncategorized | Version: SVN

Re: [Django] #10449: Bug: HTML accents not escaped out when using newforms

#10449: Bug: HTML accents not escaped out when using newforms ---+ Reporter: tipan | Owner: nobody Status: reopened | Milestone:

Re: [Django] #7258: connection in WhereNode does not come down from Query

#7258: connection in WhereNode does not come down from Query ---+ Reporter: Koen Biermans | Owner: nobody Status: reopened

[Changeset] r10029 - in django/trunk: django/db django/db/backends django/db/backends/postgresql_psycopg2 django/db/models django/db/models/sql docs/ref docs/topics/db

Author: mtredinnick Date: 2009-03-11 02:06:50 -0500 (Wed, 11 Mar 2009) New Revision: 10029 Modified: django/trunk/django/db/backends/__init__.py django/trunk/django/db/backends/postgresql_psycopg2/base.py django/trunk/django/db/models/query.py

[Django] #10461: Annotation and generic relations do not work well together

#10461: Annotation and generic relations do not work well together ---+ Reporter: mk | Owner: Status: new| Milestone: Component: ORM aggregation|

Re: [Django] #8478: Change Canadian postal code for Newfoundland

#8478: Change Canadian postal code for Newfoundland -+-- Reporter: dharris | Owner: dharris Status: closed | Milestone: Component: