#2595: get_next_by_FIELD returns itself if it is the last item, under postgres
-----------------------------------+----------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: adrian
Type: defect | Status: new
Priority: high | Milestone:
Component: Database wrapper | Version:
Severity: normal | Keywords:
-----------------------------------+----------------------------------------
Sometime in the last few days get_next_by_FIELD seems to have broken under
Postgresql. Calling {{{get_next_by_published}}}, where {{{published}}} is
a {{{DateTimeField(auto_now_add=True)}}}, on the latest item returns that
same item again. e.g.
{{{
>>> x = Post.objects.all()
>>> x
... [<Post: #3 (2006-08-23)>, <Post: #2 (2006-08-20)>, <Post: #1 (2006-08-
18)>]
>>> x[0]
... <Post: #3 (2006-08-23)>
>>> x[0].get_next_by_published()
... <Post: #3 (2006-08-23)>
}}}
Works fine under MySQL (passes all tests, and I don't see the problem).
Unfortunately I don't have enough postgres access to run the tests there.
--
Ticket URL: <http://code.djangoproject.com/ticket/2595>
Django <http://code.djangoproject.org/>
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 [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates
-~----------~----~----~----~------~----~------~--~---
