date:20110310

Re: [Django] #14642: save_as=True and generic inline in admin gives IndexError

2011-03-10 Thread Django

#14642: save_as=True and generic inline in admin gives IndexError
+--
   Reporter:  simon@…   |Owner:  nobody
 Status:  new   |Milestone:  1.3
  Component:  Forms |  Version:  1.2
 Resolution:| Keywords:  save_as generic inline
   Triage Stage:  Accepted  |Has patch:  0
Needs documentation:  0 |  Needs tests:  0
Patch needs improvement:  0 |
+--

Comment (by russellm):

 @brillgen - No, it isn't. 1.3 has been a release candidate for about a
 week, and will be finalized early next week. At this point,the only bugs
 being fixed are those that can be shown to cause catastrophic data loss,
 are regressions from 1.2, or are major problems with features added in the
 1.3 cycle.

-- 
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] #13376: Messages should have an "expire" flag

2011-03-10 Thread Django

#13376: Messages should have an "expire" flag
+
   Reporter:  ryanshow@…|Owner:  marekw2143
 Status:  assigned  |Milestone:
  Component:  Contrib apps  |  Version:  1.2-beta
 Resolution:| Keywords:  messages, expire
   Triage Stage:  Accepted  |Has patch:  1
Needs documentation:  1 |  Needs tests:  0
Patch needs improvement:  1 |
+

Comment (by bpeschier):

 After going through the "storage" discussion on the mailing list, I looked
 a bit further into the patch and spotted something related which should be
 improved: at the moment the encoding is done centrally in
 {{{storage/cookie.py}}} with hardcoded checks for types. Maintaining
 different types of restrictions becomes a real pain in the backside this
 way. It should be de-centralised to the actual restriction class (which
 brings the problem of determining which restriction should be loaded for
 the decode).

-- 
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] #14642: save_as=True and generic inline in admin gives IndexError

2011-03-10 Thread Django

#14642: save_as=True and generic inline in admin gives IndexError
+--
   Reporter:  simon@…   |Owner:  nobody
 Status:  new   |Milestone:  1.3
  Component:  Forms |  Version:  1.2
 Resolution:| Keywords:  save_as generic inline
   Triage Stage:  Accepted  |Has patch:  0
Needs documentation:  0 |  Needs tests:  0
Patch needs improvement:  0 |
+--

Comment (by brillgen):

 The issue can be confirmed as occurring as is with exactly the steps
 described by the original reporter and occurs at every instance not
 intermittently.
 I have been able to reproduce this with a fresh Django 1.2 install with no
 other models.

 Is this at all on the radar for 1.3?

-- 
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] #14396: Admin generates a query burst on ForeignKey with null = True

2011-03-10 Thread Django

#14396: Admin generates a query burst on ForeignKey with null = True
-+-
   Reporter:  piro   |Owner:  danielr
 Status:  assigned   |Milestone:
  Component: |  Version:  1.2
  django.contrib.admin   | Keywords:  admin database
 Resolution: |  performance
   Triage Stage:  Accepted   |Has patch:  1
Needs documentation:  0  |  Needs tests:  0
Patch needs improvement:  0  |
-+-

Comment (by brillgen):

 An alternative syntax which allows to at least limit the depth of the
 select related. Simple change would be to make
 list_select_related= where  is the depth parameter for
 select_related.
 Danielr's suggestion is also greate and can be implemented as another
 field...suggestion: list_select_related_fields

-- 
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] #14396: Admin generates a query burst on ForeignKey with null = True

2011-03-10 Thread Django

#14396: Admin generates a query burst on ForeignKey with null = True
-+-
   Reporter:  piro   |Owner:  danielr
 Status:  assigned   |Milestone:
  Component: |  Version:  1.2
  django.contrib.admin   | Keywords:  admin database
 Resolution: |  performance
   Triage Stage:  Accepted   |Has patch:  1
Needs documentation:  0  |  Needs tests:  0
Patch needs improvement:  0  |
-+-
Changes (by brillgen):

 * cc: brillgen (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] #14261: Add middleware for setting X-Frame-Options HTTP header in responses

2011-03-10 Thread Django

#14261: Add middleware for setting X-Frame-Options HTTP header in responses
-+-
   Reporter:  rniemeyer  |Owner:  rniemeyer
 Status:  assigned   |Milestone:
  Component:  HTTP   |  Version:  1.2
  handling   | Keywords:  clickjacking
 Resolution: |  x_frame_options
   Triage Stage:  Accepted   |Has patch:  1
Needs documentation:  1  |  Needs tests:  0
Patch needs improvement:  1  |
-+-

Comment (by rniemeyer):

 The documentation is nearly complete. Will include in updated patch
 sometime during Pycon.

-- 
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] #11203: ie not rendering correctly rtl forms

2011-03-10 Thread Django

#11203: ie not rendering correctly rtl forms
-+-
   Reporter:  hadaraz|Owner:  karahello
 Status:  assigned   |Milestone:
  Component: |  Version:  SVN
  django.contrib.admin   | Keywords:  admin css rtl
 Resolution: |Has patch:  0
   Triage Stage:  Accepted   |  Needs tests:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by karahello):

 * status:  new => assigned


-- 
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] #11203: ie not rendering correctly rtl forms

2011-03-10 Thread Django

#11203: ie not rendering correctly rtl forms
-+-
   Reporter:  hadaraz|Owner:  karahello
 Status:  new|Milestone:
  Component: |  Version:  SVN
  django.contrib.admin   | Keywords:  admin css rtl
 Resolution: |Has patch:  0
   Triage Stage:  Accepted   |  Needs tests:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by karahello):

 * cc: somarsom2000@… (added)
 * owner:  nobody => karahello


-- 
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] #15586: Fields with missing columns populated when querying on PostgreSQL

2011-03-10 Thread Django

#15586: Fields with missing columns populated when querying on PostgreSQL
-+-
   Reporter:  sebzur |Owner:  nobody
 Status:  reopened   |Milestone:
  Component:  Database   |  Version:  1.2
  layer (models, ORM)| Keywords:  postgresql
 Resolution: |Has patch:  0
   Triage Stage:  Design |  Needs tests:  0
  decision needed|
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by ramiro):

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


Comment:

 I can reproduce this with PostgreSQL 8.4.7. Reopening the ticket.

-- 
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] #15142: Contrib tests throwing errors on bare project when cache middleware enabled and cache specified

2011-03-10 Thread Django

#15142: Contrib tests throwing errors on bare project when cache middleware 
enabled
and cache specified
-+--
   Reporter:  jsdalton   |Owner:  nobody
 Status:  new|Milestone:  1.3
  Component:  Contrib apps   |  Version:  SVN
 Resolution: | Keywords:
   Triage Stage:  Ready for checkin  |Has patch:  1
Needs documentation:  0  |  Needs tests:  0
Patch needs improvement:  0  |
-+--
Changes (by russellm):

 * stage:  Accepted => Ready for checkin


Comment:

 @rakuco -- Looks like it is.

 @jsdalton -- Thanks for the analysis; the sounds reasonable to me, and
 your patch looks good from first inspection. Marking RFC to remind me to
 take a look at getting this to trunk.

-- 
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] #14105: django.contrib.auth tests failing with cache middleware

2011-03-10 Thread Django

#14105: django.contrib.auth tests failing with cache middleware
+-
   Reporter:  baumer1122|Owner:  PaulM
 Status:  closed|Milestone:
  Component:  Cache system  |  Version:  1.2
 Resolution:  duplicate | Keywords:
   Triage Stage:  Accepted  |Has patch:  0
Needs documentation:  0 |  Needs tests:  0
Patch needs improvement:  0 |
+-
Changes (by russellm):

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


Comment:

 Closing as a duplicate of #15142; This ticket came first, but the other
 ticket has a more complete analysis and a proposed patch.

-- 
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] #15130: Model.validate_unique method doesn't take in account multi-db

2011-03-10 Thread Django

#15130: Model.validate_unique method doesn't take in account multi-db
---+
   Reporter:  t2y  |Owner:
 Status:  reopened |Milestone:  1.3
  Component:  ORM aggregation  |  Version:  1.2
 Resolution:   | Keywords:  multi-db
   Triage Stage:  Accepted |Has patch:  1
Needs documentation:  0|  Needs tests:  0
Patch needs improvement:  1|
---+
Changes (by bberes):

 * cc: botondus@… (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] #15145: in is ignored by an excluded query if fooin is set to an empty iterable

2011-03-10 Thread Django

#15145: __in is ignored by an excluded query if foo__in is set to an empty 
iterable
-+-
   Reporter:  melinath   |Owner:  nobody
 Status:  new|Milestone:
  Component:  Database   |  Version:  SVN
  layer (models, ORM)| Keywords:
 Resolution: |Has patch:  0
   Triage Stage:  Accepted   |  Needs tests:  0
Needs documentation:  0  |
Patch needs improvement:  1  |
-+-
Changes (by bberes):

 * cc: botondus@… (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] #14894: translation is not threadsafe

2011-03-10 Thread Django

#14894: translation is not threadsafe
-+-
   Reporter:  maxbublis  |Owner:  nobody
 Status:  new|Milestone:  1.3
  Component:  Core   |  Version:  1.2
  framework  | Keywords:  threadsafety
 Resolution: |  translation
   Triage Stage: |Has patch:  1
  Unreviewed |  Needs tests:  1
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by bberes):

 * cc: botondus@… (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] #15593: Docs: result of reverse() is already urlquoted

2011-03-10 Thread Django

#15593: Docs: result of reverse() is already urlquoted
-+--
   Reporter:  guettli|Owner:  nobody
 Status:  new|Milestone:
  Component:  Documentation  |  Version:  1.2
 Resolution: | Keywords:
   Triage Stage:  Accepted   |Has patch:  1
Needs documentation:  0  |  Needs tests:  0
Patch needs improvement:  0  |
-+--
Changes (by gabrielhurley):

 * 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] #15266: "login_required" for "password_change_done" like "password_change"

2011-03-10 Thread Django

#15266: "login_required" for "password_change_done" like "password_change"
--+-
   Reporter:  Stephane|Owner:  lasko
 Status:  new |Milestone:
  Component:  Authentication  |  Version:
 Resolution:  | Keywords:
   Triage Stage:  Accepted|Has patch:  1
Needs documentation:  0   |  Needs tests:  0
Patch needs improvement:  0   |
--+-
Changes (by lasko):

 * owner:  nobody => lasko


-- 
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] #15586: Fields with missing columns populated when querying on PostgreSQL

2011-03-10 Thread Django

#15586: Fields with missing columns populated when querying on PostgreSQL
-+-
   Reporter:  sebzur |Owner:  nobody
 Status:  closed |Milestone:
  Component:  Database   |  Version:  1.2
  layer (models, ORM)| Keywords:  postgresql
 Resolution:  needsinfo  |Has patch:  0
   Triage Stage:  Design |  Needs tests:  0
  decision needed|
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-

Comment (by sebzur):

 I was using Django 1.2.3, Postgres 9.0.1, psycopg2 v. 2.2.2 (dt dec ext
 pq3). In a few hours I'll try once again, with a raw SQL query and I'll
 report the results. I'll try to test it also with Postgres 8.

-- 
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] #15142: Contrib tests throwing errors on bare project when cache middleware enabled and cache specified

2011-03-10 Thread Django

#15142: Contrib tests throwing errors on bare project when cache middleware 
enabled
and cache specified
+--
   Reporter:  jsdalton  |Owner:  nobody
 Status:  new   |Milestone:  1.3
  Component:  Contrib apps  |  Version:  SVN
 Resolution:| Keywords:
   Triage Stage:  Accepted  |Has patch:  1
Needs documentation:  0 |  Needs tests:  0
Patch needs improvement:  0 |
+--

Comment (by rakuco):

 Hi there.

 Isn't this a duplicate of ticket #14105?

-- 
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] #15586: Fields with missing columns populated when querying on PostgreSQL

2011-03-10 Thread Django

#15586: Fields with missing columns populated when querying on PostgreSQL
-+-
   Reporter:  sebzur |Owner:  nobody
 Status:  closed |Milestone:
  Component:  Database   |  Version:  1.2
  layer (models, ORM)| Keywords:  postgresql
 Resolution:  needsinfo  |Has patch:  0
   Triage Stage:  Design |  Needs tests:  0
  decision needed|
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-

Comment (by lrekucki):

 Could you try with PostgreSQL >= 8.4 ? I was using PostgreSQL 8.4.7 and
 psycopg2 2.3.2. Only reference to a similar problem I could find is:
 http://archives.postgresql.org/pgsql-general/2010-05/msg01126.php.

-- 
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] #15586: Fields with missing columns populated when querying on PostgreSQL

2011-03-10 Thread Django

#15586: Fields with missing columns populated when querying on PostgreSQL
-+-
   Reporter:  sebzur |Owner:  nobody
 Status:  closed |Milestone:
  Component:  Database   |  Version:  1.2
  layer (models, ORM)| Keywords:  postgresql
 Resolution:  needsinfo  |Has patch:  0
   Triage Stage:  Design |  Needs tests:  0
  decision needed|
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by ramiro):

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


Comment:

 I can't reproduce this. Tried with Django trunk and 1.2.5

 * PostgresSQL version is 8.3.14
 * psycopg2 version is 2.0.7-4

 {{{
 #!python
 # t15586/models.py

 from django.db import models

 class MyModel(models.Model):
 name = models.CharField(max_length=255)
 }}}

 {{{
 $ ./manage.py dbshell
 Welcome to psql 8.3.14, the PostgreSQL interactive terminal.

 Type:  \copyright for distribution terms
\h for help with SQL commands
\? for help with psql commands
\g or terminate with semicolon to execute query
\q to quit

 dbname=> select * from t15586_mymodel;
  id
 
 (0 rows)

 dbname=>

 }}}

 {{{
 $ ./manage.py shell
 Python 2.5.2 (r252:60911, Jan 24 2010, 14:53:14)
 Type "copyright", "credits" or "license" for more information.

 IPython 0.8.4 -- An enhanced Interactive Python.
 ? -> Introduction and overview of IPython's features.
 %quickref -> Quick reference.
 help  -> Python's own help system.
 object?   -> Details about 'object'. ?object also works, ?? prints more.

 In [1]: from django.db import connection

 In [2]: from t15586.models import MyModel

 In [3]: MyModel.objects.all()
 Out[3]:
 ---
 DatabaseError Traceback (most recent call
 last)

 dtest07/ in ()

 /var/lib/python-support/python2.5/IPython/Prompts.pyc in __call__(self,
 arg)
 549
 550 # and now call a possibly user-defined print mechanism
 --> 551 manipulated_val = self.display(arg)
 552
 553 # user display hooks can change the variable to be
 stored in

 /var/lib/python-support/python2.5/IPython/Prompts.pyc in _display(self,
 arg)
 575 return IPython.generics.result_display(arg)
 576 except TryNext:
 --> 577 return self.shell.hooks.result_display(arg)
 578
 579 # Assign the default display method:

 /var/lib/python-support/python2.5/IPython/hooks.pyc in __call__(self,
 *args, **kw)
 133 #print "prio",prio,"cmd",cmd #dbg
 134 try:
 --> 135 ret = cmd(*args, **kw)
 136 return ret
 137 except ipapi.TryNext, exc:

 /var/lib/python-support/python2.5/IPython/hooks.pyc in
 result_display(self, arg)
 163
 164 if self.rc.pprint:
 --> 165 out = pformat(arg)
 166 if '\n' in out:
 167 # So that multi-line strings line up with the left
 column of

 /usr/lib/python2.5/pprint.pyc in pformat(self, object)
 109 def pformat(self, object):
 110 sio = _StringIO()
 --> 111 self._format(object, sio, 0, 0, {}, 0)
 112 return sio.getvalue()
 113

 /usr/lib/python2.5/pprint.pyc in _format(self, object, stream, indent,
 allowance, context, level)
 127 self._readable = False
 128 return
 --> 129 rep = self._repr(object, context, level - 1)
 130 typ = _type(object)
 131 sepLines = _len(rep) > (self._width - 1 - indent -
 allowance)

 /usr/lib/python2.5/pprint.pyc in _repr(self, object, context, level)
 193 def _repr(self, object, context, level):
 194 repr, readable, recursive = self.format(object,
 context.copy(),
 --> 195 self._depth,
 level)
 196 if not readable:
 197 self._readable = False

 /usr/lib/python2.5/pprint.pyc in format(self, object, context, maxlevels,
 level)
 205 and whether the object represents a recursive construct.
 206 """
 --> 207 return _safe_repr(object, context, maxlevels, level)
 208
 209

 /usr/lib/python2.5/pprint.pyc in _safe_repr(object, context, maxlevels,
 level)
 290 return format % _commajoin(components), readable,
 recursive
 291
 --> 292 rep = repr(object)
 293 return rep, (rep and not rep.startswith('<')), False
 294

 django/db/models/query.py in __repr__(self)
  65
  66 def __repr__(self):
 ---> 67 data = list(self[:REPR_OUTPUT_SIZE + 1])
  68 if len(data) > REPR_OUTPUT

Re: [Django] #14760: Admin inlines with file/image field fails to save_as

2011-03-10 Thread Django

#14760: Admin inlines with file/image field fails to save_as
--+--
   Reporter:  paulos  |Owner:  nobody
 Status:  reopened|Milestone:
  Component:  django.contrib.admin|  Version:  1.2
 Resolution:  | Keywords:
   Triage Stage:  Design decision needed  |Has patch:  0
Needs documentation:  0   |  Needs tests:  0
Patch needs improvement:  0   |
--+--

Comment (by russellm):

 To remove any illusions -- this *will not* happen for 1.3. 1.3 is now a
 release candidate; the only fixes being applied at this point are for
 critical bugs.

-- 
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] #14760: Admin inlines with file/image field fails to save_as

2011-03-10 Thread Django

#14760: Admin inlines with file/image field fails to save_as
--+--
   Reporter:  paulos  |Owner:  nobody
 Status:  reopened|Milestone:
  Component:  django.contrib.admin|  Version:  1.2
 Resolution:  | Keywords:
   Triage Stage:  Design decision needed  |Has patch:  0
Needs documentation:  0   |  Needs tests:  0
Patch needs improvement:  0   |
--+--
Changes (by dokterbob):

 * cc: mathijs@… (added)


Comment:

 Any news on the design decision here? Whether the 'physical' file gets
 duplicated or not, it'd be great to see this issue fixed when 1.3 comes
 out - or some time soon thereafter.

 When making this decision, I reckon it is important to consider the
 consequences of both strategies:
 1. Only the reference gets duplicated: this might conflict slightly with
 the users' expectation of the saved object getting duplicated. However, it
 seems to me there are no further consequences. Unlike the related inline
 objects, which are in fact duplicated, file objects are not usually
 changed in place. Moreover, copying a file object might be an 'expensive'
 operation in that it takes up CPU while doing so, will take up disk space
 _and_ will potentially hurt client cache efficiency.
 2. The stored file object will be duplicated and the new object will
 contain a reference to this new file. As stated above, this will imply a
 loss of efficiency with regards to storage, CPU and - potentially - server
 traffic. However, it is the only solution fully consistent with the
 expected behaviour from the user side. Also, it is the only behaviour that
 allows for in-place editing of file objects in a consistent manner.

 Generally, I think it would be wise to go with option 2 by default as the
 other option might cause unexpected errors due to unconsistent behaviour.
 This is potentially harmful as it might lead to dataloss when files are
 somehow edited in-place. Option 1 might, however, be a neat optional
 feature - perhaps to be included in a 1.3.X release.

 Just a thought. :)

-- 
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] #5681: Save as new disappears on failed validation

2011-03-10 Thread Django

#5681: Save as new disappears on failed validation
-+-
   Reporter:  Uninen |Owner:  nobody
 Status:  new|Milestone:
  Component: |  Version:  SVN
  django.contrib.admin   | Keywords:  admin, save
 Resolution: |Has patch:  0
   Triage Stage:  Design |  Needs tests:  1
  decision needed|
Needs documentation:  0  |
Patch needs improvement:  1  |
-+-
Changes (by dokterbob):

 * cc: mathijs@… (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] #5423: "dumpdata" should stream output one row at a time

2011-03-10 Thread Django

#5423: "dumpdata" should stream output one row at a time
-+-
   Reporter:  adrian |Owner:  ramiro
 Status:  assigned   |Milestone:
  Component: |  Version:  SVN
  Serialization  | Keywords:  dumpdata fixtures
 Resolution: |  memory
   Triage Stage:  Accepted   |Has patch:  1
Needs documentation:  0  |  Needs tests:  0
Patch needs improvement:  0  |
-+-

Comment (by Boris Savelev ):

 I try dumpdata with latest patch
 python manage.py dumpdata -a > dump.json

 at the end of work from `top`:
 446m 429m 3460 R 96.4 12.3   2:54.07 python manage.py dumpdata -a

 ls -lha dump.json
 -rw-r--r-- 1 boris boris 77M Мар 10 17:50 dump.json

 I din't think that it is ok.

 Also, dumpdata doesn't flush data on disk while working
 data flush only at the end

-- 
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] #3111: newforms: Add as_tr(), as_li() methods to BoundField

2011-03-10 Thread Django

#3111: newforms: Add as_tr(), as_li() methods to BoundField
+-
   Reporter:  brantley  |Owner:  aashu_dwivedi
 Status:  assigned  |Milestone:
  Component:  Forms |  Version:
 Resolution:| Keywords:
   Triage Stage:  Accepted  |Has patch:  0
Needs documentation:  0 |  Needs tests:  0
Patch needs improvement:  0 |
+-
Changes (by aashu_dwivedi):

 * owner:   => aashu_dwivedi
 * status:  new => assigned


-- 
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] #15258: Ajax CSRF protection doesn't apply to PUT or DELETE requests

2011-03-10 Thread Django

#15258: Ajax CSRF protection doesn't apply to PUT or DELETE requests
--+-
   Reporter:  brodie  |Owner:  nobody
 Status:  new |Milestone:  1.4
  Component:  Core framework  |  Version:  1.2
 Resolution:  | Keywords:  csrf ajax
   Triage Stage:  Accepted|Has patch:  1
Needs documentation:  0   |  Needs tests:  1
Patch needs improvement:  0   |
--+-
Changes (by lukeplant):

 * milestone:   => 1.4


Comment:

 I agree with both points made by tow21.

 Given that the current CSRF protection works as advertised, we have to
 regard this as a feature request, not a bug, so it will have to go into
 1.4 now. Also, given the fact the protection will be extended to methods
 besides POST, it will need a 'backwards compatibility' note in the release
 notes for 1.4.

 Other than these things, I don't think much more needs to be done on this.

-- 
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] #15585: Login view should call an empty hook in the authentication form

2011-03-10 Thread Django

#15585: Login view should call an empty hook in the authentication form
--+--
   Reporter:  freyley |Owner:  nobody
 Status:  closed  |Milestone:
  Component:  Authentication  |  Version:  1.2
 Resolution:  wontfix | Keywords:
   Triage Stage:  Unreviewed  |Has patch:  1
Needs documentation:  0   |  Needs tests:  0
Patch needs improvement:  0   |
--+--
Changes (by lukeplant):

 * status:  new => closed
 * needs_docs:   => 0
 * resolution:   => wontfix
 * needs_tests:   => 0
 * needs_better_patch:   => 0


Comment:

 I'm pretty sure that this can easily be achieved by use of the
 [http://docs.djangoproject.com/en/dev/topics/auth/#login-and-logout-
 signals user_logged_in] signal. Please re-open if there is a reason this
 will not work.

-- 
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] #15577: inefficient design of inlinemodeladmin

2011-03-10 Thread Django

#15577: inefficient design of inlinemodeladmin
+--
   Reporter:  yoav@…|Owner:  nobody
 Status:  closed|Milestone:
  Component:  django.contrib.admin  |  Version:  1.2
 Resolution:  invalid   | Keywords:
   Triage Stage:  Unreviewed|Has patch:  0
Needs documentation:  0 |  Needs tests:  0
Patch needs improvement:  0 |
+--

Comment (by yoav@…):

 Perhaps this is an RTFM issue, but we failed to notice this or figure out
 the subtleties when reading through the documentation.

 To some extent, we'd expect the opposite from the default behaviour. i.e.
 That the Inline would use just the linked foreign fields by default
 instead of loading all objects, and only if you really want to load ALL
 objects, you can specify it the other way. The way we looked at it was
 that the Inline allows you to access other fields that are a part of this
 relationship, not others which are not.

 In any case it was an interesting learning experience.

-- 
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] #15586: Fields with missing columns populated when querying on PostgreSQL

2011-03-10 Thread Django

#15586: Fields with missing columns populated when querying on PostgreSQL
-+-
   Reporter:  sebzur |Owner:  nobody
 Status:  reopened   |Milestone:
  Component:  Database   |  Version:  1.2
  layer (models, ORM)| Keywords:  postgresql
 Resolution: |Has patch:  0
   Triage Stage:  Design |  Needs tests:  0
  decision needed|
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by bberes):

 * cc: botondus@… (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] #15592: Typo in syndication docs

2011-03-10 Thread Django

#15592: Typo in syndication docs
---+--
   Reporter:  bradley.ayers@…  |Owner:  nobody
 Status:  new  |Milestone:  1.3
  Component:  Documentation|  Version:  SVN
 Resolution:   | Keywords:
   Triage Stage:  Accepted |Has patch:  1
Needs documentation:  0|  Needs tests:  0
Patch needs improvement:  0|
---+--
Changes (by bberes):

 * has_patch:  0 => 1


-- 
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] #13896: Change language to dynamic attribute in syndication feed generator

2011-03-10 Thread Django

#13896: Change language to dynamic attribute in syndication feed generator
-+
   Reporter:  jedie  |Owner:  jasonkotenko
 Status:  assigned   |Milestone:
  Component:  RSS framework  |  Version:  SVN
 Resolution: | Keywords:
   Triage Stage:  Accepted   |Has patch:  1
Needs documentation:  0  |  Needs tests:  0
Patch needs improvement:  0  |
-+

Comment (by ChrisMorgan):

 It would be very nice if this could get put into Django 1.3. I've had to
 hack this into shape myself to get it working for the new Inkscape website
 which can make news feeds for any supported language, using
 request.LANGUAGE_CODE rather than settings.LANGUAGE_CODE (seems to me that
 that is going to be a common request; I think it would be good if Feed
 stored the Request - but that's another ticket).

 See http://bazaar.launchpad.net/~inkscape-webadmin/inkscape-web/inkscape-
 web/revision/62 for how I ended up wedging it in (1.2.5): and I ''know''
 it won't work even back in 1.2.3 due to a couple of changes in the Django
 code, without providing another couple of methods. Not very maintainable
 :-(

-- 
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] #15577: inefficient design of inlinemodeladmin

2011-03-10 Thread Django

#15577: inefficient design of inlinemodeladmin
+--
   Reporter:  yoav@…|Owner:  nobody
 Status:  closed|Milestone:
  Component:  django.contrib.admin  |  Version:  1.2
 Resolution:  invalid   | Keywords:
   Triage Stage:  Unreviewed|Has patch:  0
Needs documentation:  0 |  Needs tests:  0
Patch needs improvement:  0 |
+--
Changes (by anonymous):

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


Comment:

 Absent a specific suggestion for what to put in the documentation, it's
 hard to do anything useful here.

 You can in fact add a new entry, after clicking the looking-glass icon.
 That will bring up a panel where you can search for and choose from an
 existing object or (in the upper right) create a new one.

-- 
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] #11707: limit_choices_to on a ForeignKey can render duplicate options in formfield

2011-03-10 Thread Django

#11707: limit_choices_to on a ForeignKey can render duplicate options in 
formfield
-+-
   Reporter: |Owner:  nobody
  Chris.Wesseling@…  |Milestone:
 Status:  reopened   |  Version:  SVN
  Component:  Forms  | Keywords:  ForeingKey
 Resolution: |  limit_choices_to
   Triage Stage:  Accepted   |Has patch:  1
Needs documentation:  0  |  Needs tests:  0
Patch needs improvement:  1  |
-+-

Comment (by anonymous):

 Replying to [comment:11 charstring]:
 > Replying to [comment:7 lukeplant]:
 > > {{{
 > > #!CommitTicketReference repository="" revision="15791"
 > > Fixed #15559 - distinct queries introduced by [15607] cause errors
 with some custom model fields
 > > }}}
 >
 > Can someone point me to an example of such a custom model field or, even
 better, a test showing the breakage?

 The discussion linked from the description of the other ticket has an
 example. It's in dpaste so may not be long-lived. Copying here for
 reference:

 {{{
 #!python
 class PointField(models.Field):
 description = _("A geometric point")

 __metaclass__ = models.SubfieldBase

 pattern = re.compile('^\(([\d\.]+),([\d\.]+)\)$')

 def db_type(self, connection):
 if connection.settings_dict['ENGINE'] is not
 'django.db.backends.postgresql_psycopg2':
 return None

 return 'point'

 def to_python(self, value):
 if isinstance(value, tuple):
 return (float(value[0]), float(value[1]))

 if not value:
 return (0, 0)

 match = self.pattern.findall(value)[0]
 return (float(match[0]), float(match[1]))

 def get_prep_value(self, value):
 return self.to_python(value)

 def get_db_prep_value(self, value, connection, prepared=False):
 # Casts dates into the format expected by the backend
 if not prepared:
 value = self.get_prep_value(value)
 return '({0}, {1})'.format(value[0], value[1])

 def get_prep_lookup(self, lookup_type, value):
 raise TypeError('Lookup type %r not supported.' % lookup_type)

 def value_to_string(self, obj):
 value = self._get_val_from_obj(obj)
 return self.get_db_prep_value(value)
 }}}

-- 
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] #15258: Ajax CSRF protection doesn't apply to PUT or DELETE requests

2011-03-10 Thread Django

#15258: Ajax CSRF protection doesn't apply to PUT or DELETE requests
--+-
   Reporter:  brodie  |Owner:  nobody
 Status:  new |Milestone:
  Component:  Core framework  |  Version:  1.2
 Resolution:  | Keywords:  csrf ajax
   Triage Stage:  Accepted|Has patch:  1
Needs documentation:  0   |  Needs tests:  1
Patch needs improvement:  0   |
--+-

Comment (by tow21):

 To respond to the "tricky thing" in the original report: DELETE has no
 body, so there's no way to pass the token in the body anyway. And since
 PUT may contain essentially arbitrary data that need not be form-encoded,
 I think it's reasonable to require use of X-CSRFToken instead.

 Additionally, I think the patch perhaps ought to be changed so that
 instead of:

 {{{
 - if request.method == 'POST':
 + if request.method in ('POST', 'PUT', 'DELETE'):
 }}}

 we do:

 {{{
 - if request.method == 'POST':
 + if request.method not in ('GET', 'HEAD', 'OPTIONS'):
 }}}

 Rationale: if anyone is experimenting with methods beyond those in HTTP
 itself (for example, writing handlers for WebDAV methods) then we have no
 guarantees on the idempotency of anything other than GET, HEAD, and
 OPTIONS.

-- 
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] #15592: Typo in syndication docs

2011-03-10 Thread Django

#15592: Typo in syndication docs
---+--
   Reporter:  bradley.ayers@…  |Owner:  nobody
 Status:  new  |Milestone:  1.3
  Component:  Documentation|  Version:  SVN
 Resolution:   | Keywords:
   Triage Stage:  Accepted |Has patch:  0
Needs documentation:  0|  Needs tests:  0
Patch needs improvement:  0|
---+--
Changes (by ramiro):

 * needs_better_patch:   => 0
 * stage:  Unreviewed => Accepted
 * needs_tests:   => 0
 * needs_docs:   => 0


-- 
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] #15591: ModelForm save() behavior contradicts with Model object validation documentation.

2011-03-10 Thread Django

#15591: ModelForm save() behavior contradicts with Model object validation
documentation.
-+-
   Reporter:  vinod@…|Owner:  nobody
 Status:  new|Milestone:
  Component: |  Version:  1.2
  Documentation  | Keywords:  modelform validation
 Resolution: |  save model object
   Triage Stage:  Accepted   |Has patch:  0
Needs documentation:  0  |  Needs tests:  0
Patch needs improvement:  0  |
-+-
Changes (by ramiro):

 * needs_better_patch:   => 0
 * needs_docs:   => 0
 * needs_tests:   => 0
 * 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] #15593: Docs: result of reverse() is already urlquoted

2011-03-10 Thread Django

#15593: Docs: result of reverse() is already urlquoted
-+--
   Reporter:  guettli|Owner:  nobody
 Status:  new|Milestone:
  Component:  Documentation  |  Version:  1.2
 Resolution: | Keywords:
   Triage Stage:  Unreviewed |Has patch:  1
Needs documentation:  0  |  Needs tests:  0
Patch needs improvement:  0  |
-+--
Changes (by guettli):

 * has_patch:  0 => 1


-- 
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] #15593: Docs: result of reverse() is already urlquoted

2011-03-10 Thread Django

#15593: Docs: result of reverse() is already urlquoted
-+--
   Reporter:  guettli|Owner:  nobody
 Status:  new|Milestone:
  Component:  Documentation  |  Version:  1.2
 Resolution: | Keywords:
   Triage Stage:  Unreviewed |Has patch:  0
Needs documentation:  0  |  Needs tests:  0
Patch needs improvement:  0  |
-+--
Changes (by guettli):

 * cc: hv@… (added)
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0


-- 
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] #15593: Docs: result of reverse() is already urlquoted

2011-03-10 Thread Django

#15593: Docs: result of reverse() is already urlquoted
---+---
 Reporter:  guettli| Owner:  nobody
   Status:  new| Milestone:
Component:  Documentation  |   Version:  1.2
 Keywords: |  Triage Stage:  Unreviewed
Has patch:  0  |
---+---
 The documentation of reverse() could be improved:

 http://docs.djangoproject.com/en/dev/topics/http/urls/#reverse

 Add a note, that the result is already urlquoted.

 Patch is attched.

-- 
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] #13839: select_related caches None for non-existent objects in reverse one-to-one relations

2011-03-10 Thread Django

#13839: select_related caches None for non-existent objects in reverse 
one-to-one
relations
-+-
   Reporter: |Owner:  nobody
  shauncutts |Milestone:  1.3
 Status:  new|  Version:  1.2
  Component:  Database   | Keywords:
  layer (models, ORM)|Has patch:  1
 Resolution: |  Needs tests:  0
   Triage Stage:  Ready for  |
  checkin|
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by TomaszZielinski):

 * cc: tomasz.zielinski@… (added)


Comment:

 Personally I rely on the None behaviour and doesn't consider it a bug, but
 it looks like I'm a minority here so I'll just look at how this ends.

-- 
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] #15577: inefficient design of inlinemodeladmin

2011-03-10 Thread Django

#15577: inefficient design of inlinemodeladmin
+--
   Reporter:  yoav@…|Owner:  nobody
 Status:  reopened  |Milestone:
  Component:  django.contrib.admin  |  Version:  1.2
 Resolution:| Keywords:
   Triage Stage:  Unreviewed|Has patch:  0
Needs documentation:  0 |  Needs tests:  0
Patch needs improvement:  0 |
+--
Changes (by yoav@…):

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


Comment:

 Thanks for pointing it out. Looks like we missed this. It might still be
 worthwhile highlighting more explicitly in the documentation?

 So using the raw_id_fields minimizes queries for the whole list, but then
 you lose the functionality you get with the little plus sign allowing you
 to add a member by name. Or maybe we're missing something out here as
 well??

-- 
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] #15592: Typo in syndication docs

2011-03-10 Thread Django

#15592: Typo in syndication docs
-+---
 Reporter:  bradley.ayers@…  | Owner:  nobody
   Status:  new  | Milestone:  1.3
Component:  Documentation|   Version:  SVN
 Keywords:   |  Triage Stage:  Unreviewed
Has patch:  0|
-+---
 Rendered is:

 {{{
 title, link and description` correspond to the standard RSS ``,
  and  elements, respectively.
 }}}

 Should be displayed as:

 {{{
 title, link and description correspond to the standard RSS , 
 and  elements, respectively.
 }}}

-- 
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] #11707: limit_choices_to on a ForeignKey can render duplicate options in formfield

2011-03-10 Thread Django

#11707: limit_choices_to on a ForeignKey can render duplicate options in 
formfield
-+-
   Reporter: |Owner:  nobody
  Chris.Wesseling@…  |Milestone:
 Status:  reopened   |  Version:  SVN
  Component:  Forms  | Keywords:  ForeingKey
 Resolution: |  limit_choices_to
   Triage Stage:  Accepted   |Has patch:  1
Needs documentation:  0  |  Needs tests:  0
Patch needs improvement:  1  |
-+-

Comment (by charstring):

 Replying to [comment:7 lukeplant]:
 > {{{
 > #!CommitTicketReference repository="" revision="15791"
 > Fixed #15559 - distinct queries introduced by [15607] cause errors with
 some custom model fields
 > }}}

 Can someone point me to an example of such a custom model field or, even
 better, a test showing the breakage?

 Replying to [comment:8 lukeplant]:
 > For future reference, a possible alternative solution might be to do
 filtering of duplicates in Python, at the point of rendering the form
 field, rather than in the database.

 Assuming 'limit_choices_to' is only used by Forms...

-- 
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] #15586: Fields with missing columns populated when querying on PostgreSQL

2011-03-10 Thread Django

#15586: Fields with missing columns populated when querying on PostgreSQL
-+-
   Reporter:  sebzur |Owner:  nobody
 Status:  reopened   |Milestone:
  Component:  Database   |  Version:  1.2
  layer (models, ORM)| Keywords:  postgresql
 Resolution: |Has patch:  0
   Triage Stage:  Design |  Needs tests:  0
  decision needed|
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by lrekucki):

 * cc: lrekucki@… (added)
 * component:  Uncategorized => Database layer (models, ORM)


-- 
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] #15586: Fields with missing columns populated when querying on PostgreSQL (was: Field populated when no DB column present)

2011-03-10 Thread Django

#15586: Fields with missing columns populated when querying on PostgreSQL
-+-
   Reporter:  sebzur |Owner:  nobody
 Status:  reopened   |Milestone:
  Component: |  Version:  1.2
  Uncategorized  | Keywords:  postgresql
 Resolution: |Has patch:  0
   Triage Stage:  Design |  Needs tests:  0
  decision needed|
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by lrekucki):

 * status:  closed => reopened
 * keywords:   => postgresql
 * resolution:  wontfix =>
 * stage:  Unreviewed => Design decision needed


Comment:

 This is a PostgreSQL related issue. The query looks something like this:
 {{{
 #!sql
 SELECT "ticket15586_mymodel"."id", "ticket15586_mymodel"."name" FROM
 "ticket15586_mymodel"
 }}}

 And with absence of {{{name}}} column on the table, one would expect it to
 fail (and it does on other SQLite). But PostgreSQL seems to let you select
 the table as a ROW object (or something like that - I'm not an expert on
 that). So the following queries are valid:

 {{{
 #!sql
 SELECT "ticket15586_mymodel" FROM "ticket15586_mymodel";
 SELECT "ticket15586_mymodel".name FROM "ticket15586_mymodel";
 SELECT ("ticket15586_mymodel")::name FROM "ticket15586_mymodel";
 }}}

 With the second being treated as the third, which is a type cast. Don't
 know if there is a way to make it unambiguous that we want a table column,
 not some weird type thing. I'm going to reopen, so maybe someone with more
 PostgreSQL-related knowledge can fix this.

-- 
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] #15586: Field populated when no DB column present

2011-03-10 Thread Django

#15586: Field populated when no DB column present
-+--
   Reporter:  sebzur |Owner:  nobody
 Status:  closed |Milestone:
  Component:  Uncategorized  |  Version:  1.2
 Resolution:  wontfix| Keywords:
   Triage Stage:  Unreviewed |Has patch:  0
Needs documentation:  0  |  Needs tests:  0
Patch needs improvement:  0  |
-+--

Comment (by sebzur):

 sorry I made a mistake - of course in second point of process workflow
 should be:

 to model was added a CharField and I did not create corresponding DB
 *column* on my own

-- 
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] #15586: Field populated when no DB column present

2011-03-10 Thread Django

#15586: Field populated when no DB column present
-+--
   Reporter:  sebzur |Owner:  nobody
 Status:  closed |Milestone:
  Component:  Uncategorized  |  Version:  1.2
 Resolution:  wontfix| Keywords:
   Triage Stage:  Unreviewed |Has patch:  0
Needs documentation:  0  |  Needs tests:  0
Patch needs improvement:  0  |
-+--

Comment (by sebzur):

 Of course testing the synchronization between the Django models & db
 schema every time would be a stupid idea - that was not my point.

 Also, I was not asking for automated schema evolution, which is quite a
 tricky issue and in most cases, for complex DB schema  updates, You just
 have to handle
 it manually on your own.

 I was just curious HOW 'SELECT' statement could retrieve something from
 database, when there was no column to get from?

 Once again I try to describe the proces:
 - model MyMode was created and db was synced
 - to model was added a CharField and I did not create corresponding DB
 table on my own
 - I performed qs = MyMode.objects.all(), that I had something in:
 qs[0].name, qs[1].name and so on ... which I do not understand how this
 field was field when there was no data in DB? It looks to me like an
 unexpected behavior

 I would appreciate Your further comments.

-- 
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.

47 matches

Mail list logo