Re: [Django] #17180: Documentation should mention that {% load i18n %} is needed in every template

[Django]

#17180: Documentation should mention that {% load i18n %} is needed in every
template
--+
 Reporter:  stefan.freyr@…|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.3
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by Buddy Lindsey ):

 * cc: buddy@… (added)


Comment:

 I submited a pull request for this with the github repository.

 https://github.com/django/django/pull/111

 Not sure if that was acceptable, but I thought I would at least try.

-- 
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] #14694: defer() doesn't work with reverse relations

[Django]

#14694: defer() doesn't work with reverse relations
-+-
 Reporter:  sayane   |Owner:  nobody
 Type:  Bug  |   Status:  reopened
Component:  Database layer   |  Version:  SVN
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  defer only   |  Needs documentation:  0
  OneToOneField reverse  |  Patch needs improvement:  1
  relationship   |UI/UX:  0
Has patch:  1|
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by mrmachine):

 Updated and re-tested against trunk.

 Fixed (and tested) one other case where passing in the `related_name` for
 a reverse `OneToOneField` to `.only()` (e.g.
 `Item.objects.only('one_to_one_item')`) would result in a silenced
 exception (triggered by attempting to access `field.column` when `field`
 is a `RelatedObject`) and an empty queryset when evaluated.

 This problem wasn't obvious with `.defer()`, or when referencing fields on
 a reverse related model with `.only()` (e.g.
 `Item.objects.only('one_to_one_item__name')`).

 I think this is a clear bug, and the patch RFC. Just awaiting review by
 another set of eyes more familiar with the 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] #13614: Back button breaks many to many widget

[Django]

#13614: Back button breaks many to many widget
---+
 Reporter:  minarets   |Owner:  nobody
 Type:  Bug|   Status:  reopened
Component:  contrib.admin  |  Version:  1.3
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  1
---+

Comment (by julien):

 Just a quick note: there has been some recent discussions between the
 chromium guys about the root cause of this issue:
 http://code.google.com/p/chromium/issues/detail?id=76739

 ... although I'm not sure if there's any chance for them to fix it before
 Django 1.4 lands.

 This is a bug in Chrome/Webkit, not in Django. However we might decide to
 fix our own code to get around it. In any case, selenium tests should be
 written to ensure the patch doesn't introduce regressions.

-- 
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] #17662: Adds percentage filter to humanize module

[Django]

#17662: Adds percentage filter to humanize module
-+-
 Reporter:  eire1130 |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  contrib.humanize |  Version:  SVN
 Severity:  Normal   |   Resolution:
 Keywords:  humanize | Triage Stage:  Design
Has patch:  1|  decision needed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  1|  Patch needs improvement:  1
 |UI/UX:  0
-+-

Comment (by akaariai):

 Hmmh, I wonder if the best approach would be to just have a filter
 |multiply "100".

 Then you could do {{ val|multiply 100}}% and let number formatting deal
 with all the ugly details of what to do for rounding etc.

-- 
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] #17662: Adds percentage filter to humanize module

[Django]

#17662: Adds percentage filter to humanize module
-+-
 Reporter:  eire1130 |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  contrib.humanize |  Version:  SVN
 Severity:  Normal   |   Resolution:
 Keywords:  humanize | Triage Stage:  Design
Has patch:  1|  decision needed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  1|  Patch needs improvement:  1
 |UI/UX:  0
-+-
Changes (by akaariai):

 * stage:  Accepted => Design decision needed


Comment:

 I was thinking that context.use_l10n would be available, but I see it is
 not available for filters. This is a bit sad, as now the percentage filter
 doesn't respect {% localize on/off %} controls. I don't know what there is
 to do about this. Not localizing the value seems inconsistent, and not
 honoring the localize on/off controls seems even worse.

 Any opinions? Maybe you should go with your first version. But then
 .format isn't available before Python 2.6.

-- 
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] #17662: Adds percentage filter to humanize module

[Django]

#17662: Adds percentage filter to humanize module
--+
 Reporter:  eire1130  |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  contrib.humanize  |  Version:  SVN
 Severity:  Normal|   Resolution:
 Keywords:  humanize  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  1 |UI/UX:  0
--+

Comment (by eire1130):

 Here's a patch using django.utils.formats.number_format. I'm not checking
 for for USE_L10N or USE_THOUSAND_SEPARATOR explicitly, because
 django.utils.formats.number_format and django.utils.numberformat already
 check for it.

 I still needed to use round(value) because numberformat doesn't give
 predictable rounding (the unit-tests were failing).

-- 
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] #17653: using id = 0 on get_or_create

[Django]

#17653: using id = 0 on get_or_create
-+-
 Reporter:  sylvain.lebon@…  |Owner:
 Type:  Bug  |  krzysiumed
Component:  Database layer   |   Status:  assigned
  (models, ORM)  |  Version:  1.3
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by akaariai):

 * needs_better_patch:  0 => 1
 * has_patch:  0 => 1


Comment:

 I was just writing a patch for this :)

 I will post what I have in case that is helpful and leave this to
 krzysiumed.

-- 
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] #17653: using id = 0 on get_or_create

[Django]

#17653: using id = 0 on get_or_create
-+-
 Reporter:  sylvain.lebon@…  |Owner:
 Type:  Bug  |  krzysiumed
Component:  Database layer   |   Status:  assigned
  (models, ORM)  |  Version:  1.3
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by krzysiumed):

 * status:  new => assigned
 * owner:  nobody => krzysiumed


-- 
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] #17662: Adds percentage filter to humanize module

[Django]

#17662: Adds percentage filter to humanize module
--+
 Reporter:  eire1130  |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  contrib.humanize  |  Version:  SVN
 Severity:  Normal|   Resolution:
 Keywords:  humanize  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  1 |UI/UX:  0
--+

Comment (by akaariai):

 From [http://docs.python.org/library/stdtypes.html#str.format| Python's
 documentation] it seems format is only available 2.6 onwards. I don't know
 what is going to be the minimum required Python version for Django 1.5,
 either 2.5 or 2.6. So, that could be a problem.

 But looking more closely at this, it seems you should use the localization
 framework of Django in some way or another. I guess the best way would be
 to format according to what django.utils.formats.numberformat gives you.
 Then you would not need to worry about decimal places, numberformat would
 do that automatically for you. You should also check the use_l10n variable
 from the context and pass it on to the numberformat. This should make the
 tag more consistent with rest of Django, and also easier to write.

-- 
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] #17662: Adds percentage filter to humanize module

[Django]

#17662: Adds percentage filter to humanize module
--+
 Reporter:  eire1130  |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  contrib.humanize  |  Version:  SVN
 Severity:  Normal|   Resolution:
 Keywords:  humanize  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  1 |UI/UX:  0
--+

Comment (by eire1130):

 I believe str.format("{':.places%'}") rounds "correctly", example:

 >>>myfloat= .56784

 >>>print "{:.2%}".format(myfloat)

 56.78%

 >>>myfloat = .56785

 >>>print "{:.2%}".format(myfloat)

 56.78%

 >>>myfloat = .56786

 >>>print "{:.2%}".format(myfloat)

 56.79%

 (note the .5 case rounds down to 0 and .51 rounds up to 1)

 Although, this has me thinking. I'm not certain if the .format method is
 available in Python 2.5X branch (maybe it is in the future module, but I
 don't have a working branch of 2.5 on this machine)

 Either way, would you like me to proceed utilizing decimal, or go with the
 string format.

-- 
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] #17659: django_admin_log searches are slow

[Django]

#17659: django_admin_log searches are slow
--+
 Reporter:  anonymous |Owner:  keeff
 Type:  Cleanup/optimization  |   Status:  new
Component:  contrib.admin |  Version:  1.3
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by akaariai):

 * needs_better_patch:  0 => 1
 * has_patch:  0 => 1
 * stage:  Unreviewed => Accepted


Comment:

 I wonder if it is really necessary to have the index for object_repr alone
 though. Every django installation using admin would need to pay the price
 of that index, but it is not needed in stock installations. I have written
 multiple django apps, and never needed object_repr lookups. You can add
 the index by hand if needed.

 So, I would say +1 on the object_id index, and more proof for the need of
 object_repr index.

 Marking as accepted on the basis of need for object_id index. Although
 query plans with the index and without it are still missing.

-- 
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] #17659: django_admin_log searches are slow

[Django]

#17659: django_admin_log searches are slow
-+-
 Reporter:  anonymous|Owner:  keeff
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.3
Component:  contrib.admin|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by anonymous):

 object_id is used in stock django, i.e. history_view() in
 contrib/admin/options.py.  The index here is a clear win for any who use
 django_admin_log.

 object_repr is often used in custom forms and other external code, one
 common example is to implement a global history search.  Doing this via
 object_id is not reasonable since this would involve working out the
 object_id for all matching objects in every extant model, and even then it
 may not be viable to match history for deleted objects.  Such forms should
 be efficient without needing a local modification to
 contrib/admin/models.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] #17662: Adds percentage filter to humanize module

[Django]

#17662: Adds percentage filter to humanize module
--+
 Reporter:  eire1130  |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  contrib.humanize  |  Version:  SVN
 Severity:  Normal|   Resolution:
 Keywords:  humanize  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  1 |UI/UX:  0
--+
Changes (by akaariai):

 * cc: anssi.kaariainen@… (added)
 * needs_docs:   => 0
 * needs_better_patch:   => 1
 * needs_tests:   => 0
 * stage:  Unreviewed => Accepted


Comment:

 I am in general in support of this, as I can see the need for this common
 enough to include in Django.

 I wonder if you should use decimal.Decimal instead to get proper rounding.
 If I am not mistaken the string formatting just truncates the value. I
 will mark the patch as needs improvement for that reason.

-- 
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] #17663: Method "save" in BaseModelFormSet is not marked as alters_data

[Django]

#17663: Method "save" in BaseModelFormSet is not marked as alters_data
-+
 Reporter:  aiv  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Forms|  Version:  SVN
 Severity:  Normal   |   Resolution:
 Keywords:  formset  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+
Changes (by akaariai):

 * cc: anssi.kaariainen@… (added)
 * needs_better_patch:   => 0
 * needs_tests:   => 1
 * easy:  0 => 1
 * needs_docs:   => 0
 * stage:  Unreviewed => Accepted


Comment:

 Makes sense. I wonder if this kind of patch needs tests. We don't have
 tests for the existing .alters_data ones. Adding a test is of course easy,
 just check that the function's alters_data attr is True. So, my initial
 feeling is why not? I guess the right place is in
 regressiontests/model_forms_regress/tests.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] #16304: Add HTML5 'placeholder' attribute support to form fields.

[Django]

#16304: Add HTML5 'placeholder' attribute support to form fields.
-+-
 Reporter:  rich@…   |Owner:  j4nu5
 Type:  New feature  |   Status:  new
Component:  Forms|  Version:  SVN
 Severity:  Normal   |   Resolution:
 Keywords:  forms, placeholder,  | Triage Stage:  Accepted
  html5  |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  1|UI/UX:  1
Easy pickings:  1|
-+-
Changes (by j4nu5):

 * status:  assigned => new
 * cc: j4nu5 (added)
 * needs_better_patch:  0 => 1
 * owner:  avenet => j4nu5
 * needs_docs:  1 => 0
 * has_patch:  0 => 1


Comment:

 I have added the said functionality to both model forms and normal forms,
 in 16304.patch.

 However, I suggest to club this ticket with a bigger undertaking of making
 Django HTML5 aware.

-- 
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] #17663: Method "save" in BaseModelFormSet is not marked as alters_data

[Django]

#17663: Method "save" in BaseModelFormSet is not marked as alters_data
+-
 Reporter:  aiv |  Owner:  nobody
 Type:  Bug | Status:  new
Component:  Forms   |Version:  SVN
 Severity:  Normal  |   Keywords:  formset
 Triage Stage:  Unreviewed  |  Has patch:  1
Easy pickings:  0   |  UI/UX:  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] #4501: Coverage support for tests

[Django]

#4501: Coverage support for tests
---+--
 Reporter:  bugs@… |Owner:  krzysiumed
 Type:  New feature|   Status:  assigned
Component:  Testing framework  |  Version:
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by IonelMaries):

 * cc: ionel.mc@… (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.

[Django] #17662: Adds percentage filter to humanize module

[Django]

#17662: Adds percentage filter to humanize module
--+--
 Reporter:  eire1130  |  Owner:  nobody
 Type:  New feature   | Status:  new
Component:  contrib.humanize  |Version:  SVN
 Severity:  Normal|   Keywords:  humanize
 Triage Stage:  Unreviewed|  Has patch:  1
Easy pickings:  1 |  UI/UX:  0
--+--
 I often find myself using a custom filter for this, and in searching
 around the internet, there seems to be others who also would like this
 built in. I searched developers and the ticket system and didn't see any
 pre-existing conversations or patches.

-- 
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] #17082: contrib.auth html should be updated to used HTML5 features where possible

[Django]

#17082: contrib.auth html should be updated to used HTML5 features where 
possible
--+
 Reporter:  drhevans  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  contrib.admin |  Version:  SVN
 Severity:  Normal|   Resolution:
 Keywords:  html5 | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by claudep):

 * keywords:   => html5


-- 
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] #17661: Foreign key with related name is not working properly.

[Django]

#17661: Foreign key with related name is not working properly.
-+-
 Reporter:  davisito89@… |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:  invalid
 Severity:  Normal   | Triage Stage:
 Keywords:  related_name |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by akaariai):

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


Comment:

 If I read your description correctly, the error is you are assuming there
 is an order for the related objects. This is not true if you don't use
 .order_by(). The related objects are not ordered, unless you order them by
 some column. The real reason this happens is that in SQL if you do:
 {{{
 select * from sometable offset 1 limit 1;
 vs
 select * from sometable offset 0 limit 1;
 }}}
 the DB is free to return the same row for the both queries. And you are
 doing multiple queries exactly like above in your code.

 Im marking this as invalid. If I am missing your problem, then reopen this
 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] #17652: LiveTestServer - we shouldn't advertise support for Windmill (or we should provide some docs)

[Django]

#17652: LiveTestServer - we shouldn't advertise support for Windmill (or we 
should
provide some docs)
-+
 Reporter:  lukeplant|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Documentation|  Version:  1.3
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by julien):

 Note: this gist contains an example with splinter:
 https://gist.github.com/1685139

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