[Django] #10426: Add a description of language environment variales to "How to use Django with Apache and mod_python" doc page

[Django]

#10426: Add a description of language environment variales to "How to use Django
with Apache and mod_python" doc page
---+
 Reporter:  daybreaker  
   |   Owner:  nobody
   Status:  new 
   |   Milestone:  1.0.3 
Component:  Documentation   
   | Version:  1.0   
 Keywords:  i18n unicode utf-8 file path apache mod_python mod_wsgi language 
environment variable  |   Stage:  Unreviewed
Has_patch:  0   
   |  
---+
 Hello, I'm a Korean user of Django.

 I've suffered from some issues on unicode file paths on mod_python, and
 finally I found the rescue
 [http://code.djangoproject.com/wiki/django_apache_and_mod_wsgi here].

 When you're going to use non-ascii filenames in your Django project
 running on Apache mod_python, the environment value for LANG should be set
 properly so that Python's os and os.path module can handle unicode
 filenames with proper encoding. There was no problem when I run my project
 with the test server included in Django because the LANG environment
 variable of my user account was set properly, but on mod_python it wasn't.

 I think the official documentation for deployment on mod_python (and maybe
 mod_wsgi also) should explain how to set the language environment variable
 properly, for example in this case, using `/etc/apache2/envvars`.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #10425: Bad SQL generated for Book.objects.values('author').annotate(Count('author')).count()

[Django]

#10425: Bad SQL generated for
Book.objects.values('author').annotate(Count('author')).count()
---+
 Reporter:  kmassey|   Owner:
   Status:  new|   Milestone:
Component:  ORM aggregation| Version:  SVN   
 Keywords:  values annotate count  |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 Observed with SVN revision 9984:

 Model:
 {{{
 class Book(models.Model):
 title = models.CharField(max_length=200)
 author = models.CharField(max_length=200)
 }}}

 When using values() with annotate(), the count() method generates bad SQL:
 {{{
 $ python manage.py shell
 Python 2.6.1 (r261:67515, Dec  6 2008, 16:42:21)
 [GCC 4.0.1 (Apple Computer, Inc. build 5370)] on darwin
 Type "help", "copyright", "credits" or "license" for more information.
 (InteractiveConsole)
 >>> from example.models import *
 >>> from django.db.models import Count
 >>> qs = Book.objects.values('author').annotate(Count('author'))
 >>> qs.count()
 Traceback (most recent call last):
   File "", line 1, in 
   File "/Users/kevin/django/bug/annotate_count/django/db/models/query.py",
 line 329, in count
 return self.query.get_count()
   File
 "/Users/kevin/django/bug/annotate_count/django/db/models/sql/query.py",
 line 345, in get_count
 number = obj.get_aggregation()[None]
   File
 "/Users/kevin/django/bug/annotate_count/django/db/models/sql/query.py",
 line 317, in get_aggregation
 result = query.execute_sql(SINGLE)
   File
 "/Users/kevin/django/bug/annotate_count/django/db/models/sql/query.py",
 line 2097, in execute_sql
 cursor.execute(sql, params)
   File
 "/Users/kevin/django/bug/annotate_count/django/db/backends/util.py", line
 19, in execute
 return self.cursor.execute(sql, params)
   File
 "/Users/kevin/django/bug/annotate_count/django/db/backends/sqlite3/base.py",
 line 190, in execute
 return Database.Cursor.execute(self, query, params)
 OperationalError: near "FROM": syntax error


 }}}

 The SQL that gets generated is malformed:
 {{{
 SELECT  FROM (SELECT "example_book"."author" AS author,
 COUNT("example_book"."author") FROM "example_book" GROUP BY
 "example_book"."author") subquery
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #8497: Please add OpenSolaris to the list of "if you already have" on the introduction

[Django]

#8497: Please add OpenSolaris to the list of "if you already have" on the
introduction
+---
  Reporter:  Matt Ingenthron   | 
Owner:  nobody
Status:  closed | 
Milestone:
 Component:  Documentation  |   
Version:  SVN   
Resolution:  invalid|  
Keywords:
 Stage:  Design decision needed | 
Has_patch:  0 
Needs_docs:  0  |   
Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by timo):

  * status:  new => closed
  * resolution:  => invalid

Comment:

 This ticket has been deprecated by #10424.  Distro-specific material will
 be moved to the [http://code.djangoproject.com/wiki/Distributions Django
 Wiki].  If you have any info about OpenSolaris and Django please add it
 there.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #10319: Installation: macports different now

[Django]

#10319: Installation: macports different now
+---
  Reporter:  thesimon   | Owner:  anonymous 
   
Status:  closed | Milestone:
   
 Component:  Documentation  |   Version:  1.0   
   
Resolution:  invalid|  Keywords:  install, documentation, 
distributions
 Stage:  Accepted   | Has_patch:  1 
   
Needs_docs:  0  |   Needs_tests:  0 
   
Needs_better_patch:  0  |  
+---
Changes (by timo):

  * status:  assigned => closed
  * resolution:  => invalid

Comment:

 This ticket has been deprecated by #10424.  Distro-specific material will
 be moved to the [http://code.djangoproject.com/wiki/Distributions Django
 Wiki].  I have updated the MacPorts version there.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9667: replace package versions with links to up-to-date searches on the distributions page

[Django]

#9667: replace package versions with links to up-to-date searches on the
distributions page
+---
  Reporter:  akaihola   | Owner:  nobody
Status:  closed | Milestone:  1.1   
 Component:  Documentation  |   Version:  SVN   
Resolution:  invalid|  Keywords:  distributions packages
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by timo):

  * status:  new => closed
  * resolution:  => invalid

Comment:

 This ticket has been deprecated by #10424.  Distro-specific material will
 be moved to the [http://code.djangoproject.com/wiki/Distributions Django
 Wiki].  I have moved much of the material from this ticket there.  Thanks!

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9606: link to django packages for openSUSE

[Django]

#9606: link to django packages for openSUSE
+---
  Reporter:  poeml  | Owner:  nobody
Status:  closed | Milestone:
 Component:  Documentation  |   Version:  1.0   
Resolution:  invalid|  Keywords:
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by timo):

  * status:  reopened => closed
  * resolution:  => invalid

Comment:

 This ticket has been deprecated by #10424.  Distro-specific material will
 be moved to the [http://code.djangoproject.com/wiki/Distributions Django
 Wiki]. I have added the example text from this ticket there.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #8417: Include the support of djangos within Archlinux

[Django]

#8417: Include the support of djangos within Archlinux
+---
  Reporter:  voidzero   | Owner:  jacob
Status:  closed | Milestone:   
 Component:  Documentation  |   Version:  SVN  
Resolution:  invalid|  Keywords:   
 Stage:  Accepted   | Has_patch:  0
Needs_docs:  0  |   Needs_tests:  0
Needs_better_patch:  0  |  
+---
Changes (by timo):

  * status:  assigned => closed
  * resolution:  => invalid

Comment:

 This ticket has been deprecated by #10424.  Distro-specific material will
 be moved to the [http://code.djangoproject.com/wiki/Distributions Django
 Wiki].  I have added your sample text to that page.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9911: Online Docs: Debian django version update

[Django]

#9911: Online Docs: Debian django version update
+---
  Reporter:  ed42   | Owner:  nobody
Status:  closed | Milestone:  1.1   
 Component:  Documentation  |   Version:  1.0   
Resolution:  invalid|  Keywords:
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by timo):

  * status:  new => closed
  * resolution:  => invalid

Comment:

 This ticket has been deprecated by #10424.  Distro-specific material will
 be moved to the [http://code.djangoproject.com/wiki/Distributions Django
 Wiki].

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #10424: revised format for docs/misc/distributions.txt

[Django]

#10424: revised format for docs/misc/distributions.txt
+---
  Reporter:  timo   | Owner:  timo 
Status:  assigned   | Milestone:  1.1  
 Component:  Documentation  |   Version:  SVN  
Resolution: |  Keywords:  distributions
 Stage:  Accepted   | Has_patch:  1
Needs_docs:  0  |   Needs_tests:  0
Needs_better_patch:  0  |  
+---
Changes (by timo):

  * status:  new => assigned
  * needs_better_patch:  => 0
  * needs_tests:  => 0
  * needs_docs:  => 0
  * has_patch:  0 => 1
  * stage:  Unreviewed => Accepted

Comment:

 ...and the [http://code.djangoproject.com/wiki/Distributions
 distributions] page on the Django Wiki.  Feel free to contribute!

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #10424: revised format for docs/misc/distributions.txt

[Django]

#10424: revised format for docs/misc/distributions.txt
---+
 Reporter:  timo   |   Owner:  timo  
   Status:  new|   Milestone:  1.1   
Component:  Documentation  | Version:  SVN   
 Keywords:  distributions  |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 Per [http://groups.google.com/group/django-
 developers/browse_thread/thread/a3e99e96ff1e094 this thread] on django-
 developers, we should revise the distributions page and move distro-
 specific notes to the Django wiki so that it is easier to maintain.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #10423: Incorrect docstring (typo) for AdminSite.admin_view

[Django]

#10423: Incorrect docstring (typo) for AdminSite.admin_view
--+-
 Reporter:  gremmie   |   Owner:  nobody
   Status:  new   |   Milestone:  1.1 beta  
Component:  django.contrib.admin  | Version:  SVN   
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 The docstring for !AdminSite.admin_view shows an example usage of the
 decorator admin_view, however in the example it is spelled
 "protected_view" instead of "admin_view".

 This is in the file django/contrib/admin/sites.py.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #10405: quoted class names in foreign key definition causes 'str' object has no attribute '_default_manager'

[Django]

#10405: quoted class names in foreign key definition causes 'str' object has no
attribute '_default_manager'
+---
  Reporter:  danbrwn| Owner:  nobody
Status:  new| Milestone:  1.1   
 Component:  Uncategorized  |   Version:  1.0-alpha-2   
Resolution: |  Keywords:  foreign,key,quoted
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Comment (by ramiro):

 I have been able to reproduce this with Django trunk r9984 + mod_python +
 Apache with this minimal setup:

 A t10405 app:

 {{{
 #!python
 # models.py
 from django.db import models
 from django.forms import ModelForm

 class Extension(models.Model):
 context=models.ForeignKey('app2.station')

 class ExtensionForm(ModelForm):
 class Meta:
 model = Extension
 }}}

 {{{
 #!python
 # admin.py
 from t10405.models import Extension
 from django.contrib import admin

 admin.site.register(Extension)
 }}}

 The 'app2' application has only a models.py file:

 {{{
 #!python
 # models.py
 from django.db import models

 class station(models.Model):
 name = models.CharField(max_length=10)
 }}}

 urls.py has only the admin app activated (no app URLs).

 Bug shows itself when accessing the main admin page and shows as a pure
 text traceback when `DEBUG= False`.

 Note how t10405's `admin.py` imports models.py and this one contains a
 !ModelForm -derived class (this is also visible in the OP's traceback).
 Key thing here for the bug appearing is the !ExtensionForm's `Meta` inner-
 class definition because replacing the !ExtensionForm body with `pass` or
 completely commenting out !ExtensionForm so only the !ModelForm import is
 left makes the bug disappear.

 The traceback:

 {{{
 Mod_python error: "PythonHandler django.core.handlers.modpython"

 Traceback (most recent call last):

   File "/usr/lib/python2.4/site-packages/mod_python/apache.py", line 299,
 in HandlerDispatch
 result = object(req)

   File "/home/ramiro/src/django/trunk/django/core/handlers/modpython.py",
 line 228, in handler
 return ModPythonHandler()(req)

   File "/home/ramiro/src/django/trunk/django/core/handlers/modpython.py",
 line 201, in __call__
 response = self.get_response(request)

   File "/home/ramiro/src/django/trunk/django/core/handlers/base.py", line
 128, in get_response
 return self.handle_uncaught_exception(request, resolver, exc_info)

   File "/home/ramiro/src/django/trunk/django/core/handlers/base.py", line
 159, in handle_uncaught_exception
 callback, param_dict = resolver.resolve500()

   File "/home/ramiro/src/django/trunk/django/core/urlresolvers.py", line
 226, in resolve500
 return self._resolve_special('500')

   File "/home/ramiro/src/django/trunk/django/core/urlresolvers.py", line
 215, in _resolve_special
 callback = getattr(self.urlconf_module, 'handler%s' % view_type)

   File "/home/ramiro/src/django/trunk/django/core/urlresolvers.py", line
 200, in _get_urlconf_module
 self._urlconf_module = __import__(self.urlconf_name, {}, {}, [''])

   File "/web/djapps/dtests/urls.py", line 2, in ?
 from t10405.models import Extension

   File "/web/djapps/dtests/t10405/models.py", line 7, in ?
 class ExtensionForm(ModelForm):

   File "/home/ramiro/src/django/trunk/django/forms/models.py", line 195,
 in __new__
 opts.exclude, formfield_callback)

   File "/home/ramiro/src/django/trunk/django/forms/models.py", line 162,
 in fields_for_model
 formfield = formfield_callback(f)

   File "/home/ramiro/src/django/trunk/django/forms/models.py", line 177,
 in
 lambda f: f.formfield())

   File "/home/ramiro/src/django/trunk/django/db/models/fields/related.py",
 line 700, in formfield
 defaults = {

 AttributeError: 'str' object has no attribute '_default_manager'
 }}}

 It's worth noting that the other user reporting this on django-users
 (http://groups.google.com/group/django-
 users/browse_frm/thread/ae22023a61290c1e) also defined a !ModelForm
 subclass but in an admin.py file.

 Trying to execute `syncdb` also shows the bug (even with `DEBUG = False`)
 but with a different code path:

 {{{
 $ python manage.py syncdb
 Traceback (most recent call last):
   File "manage.py", line 11, in ?
 execute_manager(settings)
   File "/home/ramiro/src/django/trunk/django/core/management/__init__.py",
 line 350, in execute_manager
 utility.execute()
   File "/home/ramiro/src/django/trunk/django/core/management/__init__.py",
 line 295, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "/home/ramiro/src/django/trunk/django/core/management/base.py",
 line 195, in run_from_argv
 

Re: [Django] #10422: documentation of ticket #4140: manage.py with oracle database fails with ORA-06552 when a field name is a keyword

[Django]

#10422: documentation of ticket #4140: manage.py with oracle database fails with
ORA-06552 when a field name is a keyword
+---
  Reporter:  boyombo| Owner:  nobody
Status:  new| Milestone:
 Component:  Documentation  |   Version:  1.0   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by ikelly):

  * component:  Uncategorized => Documentation
  * stage:  Unreviewed => Accepted

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #10422: documentation of ticket #4140: manage.py with oracle database fails with ORA-06552 when a field name is a keyword

[Django]

#10422: documentation of ticket #4140: manage.py with oracle database fails with
ORA-06552 when a field name is a keyword
+---
  Reporter:  boyombo| Owner:  nobody
Status:  new| Milestone:
 Component:  Uncategorized  |   Version:  1.0   
Resolution: |  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by ikelly):

  * needs_better_patch:  => 0
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 Point of clarification.  Is {{{order}}} a name that you've actually
 encountered problems with?  Most keywords are safe to use as field names
 (though not recommended), and as far as I'm aware {{{order}}} is one of
 those.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #6903: Go back to old change_list view after hitting save

[Django]

#6903: Go back to old change_list view after hitting save
-+--
  Reporter:  jarrow  | Owner:  ramiro
Status:  new | Milestone:  1.1   
 Component:  django.contrib.admin|   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Design decision needed  | Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Comment (by mawimawi):

 Isn't such a "sticky" behaviour exactly what sessions are for? Why would
 you not use a session key like
 request.session['admin_' +  + '_' +  + '_filter'] =
 {'p':14, 'my_field__exact':True}
 and checking for this key when displaying the list of objects of a model?

 I'm also offering to try and implement that if this is desired.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #8747: Importing models from within `__init__.py` prevents syncdb from creating tables

[Django]

#8747: Importing models from within `__init__.py` prevents syncdb from creating
tables
---+
  Reporter:  julien| Owner:  nobody
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by lsaffre):

 I had probably the same problem, but less clear. I also imported models
 from the application's {{{__init__.py}}}, but the problem appeared only
 when I added another class definition (not a Model). I used {{{manage.py
 testserver}}}. It seemed that the whole application didn't get "activated"
 (also fixtures were not loaded) when this additional class definition was
 there. But no error message, not even when using {{{-v 2}}}. Also no error
 when importing these modules from a shell.
 It stopped when I moved the additional code to another module and not
 importing it in {{{__init__.py}}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9964: Transaction middleware closes the transaction only when it's marked as dirty

[Django]

#9964: Transaction middleware closes the transaction only when it's marked as
dirty
---+
  Reporter:  ishirav   | Owner:  
mtredinnick 
Status:  assigned  | Milestone:  1.1
 
 Component:  Database layer (models, ORM)  |   Version:  1.0-beta-1 
 
Resolution:|  Keywords:  
transactions
 Stage:  Accepted  | Has_patch:  0  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Comment (by jdunck):

 The obvious question is when set_dirty should be called; the description
 of this ticket suggests that a transaction should be dirty even for a
 transaction consisting only of selects.  The problem with this is that
 lots of transaction cycles are only selects, and committing a transaction
 has overhead.  I think select-only transactions should rollback by
 default.  If you're using triggers that munge data upon select, set_dirty
 should be manually called; this can be clearly documented.

 There's some overhead and fiddliness with db.connection.cursor.execute
 looking at the string it receives in order to determine CUD operations.
 Maybe backends.DatabaseOperations should have a .is_select(sql) hook?

 Otherwise it'd be a decent compromise to just clearly document more that
 only dirty transactions are committed, and that using cursor.execute does
 not mark a transaction as dirty.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9964: Transaction middleware closes the transaction only when it's marked as dirty

[Django]

#9964: Transaction middleware closes the transaction only when it's marked as
dirty
---+
  Reporter:  ishirav   | Owner:  
mtredinnick 
Status:  assigned  | Milestone:  1.1
 
 Component:  Database layer (models, ORM)  |   Version:  1.0-beta-1 
 
Resolution:|  Keywords:  
transactions
 Stage:  Accepted  | Has_patch:  0  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Changes (by jdunck):

 * cc: jdu...@gmail.com (added)

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #10421: Tutorial code

[Django]

#10421: Tutorial code
+---
  Reporter:  sam_   | Owner:  nobody
Status:  new| Milestone:
 Component:  Documentation  |   Version:  1.0   
Resolution: |  Keywords:  style 
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by ramiro):

  * needs_better_patch:  => 0
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 Could you please explain what do you mean with "hightlighted in the green
 box"?.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #10422: documentation of ticket #4140: manage.py with oracle database fails with ORA-06552 when a field name is a keyword

[Django]

#10422: documentation of ticket #4140: manage.py with oracle database fails with
ORA-06552 when a field name is a keyword
---+
 Reporter:  boyombo|   Owner:  nobody
   Status:  new|   Milestone:
Component:  Uncategorized  | Version:  1.0   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 the django documentation should have a note in the section on supported
 databases to warn developers planning to deploy on oracle that they may
 have issues running syncdb if they have models with field names which are
 keywords in oracle, for example; 'date', and 'order'.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---