I'm working on getting the SQL Anywhere backend to pass the test suite
for the current Django development branch. I've run into a number of
tests that are failing intermittently due to the order in which results
are returned. For example, the regressiontests/null_fk test sometimes
fails with:
Failed example:
[(c.id, c.comment_text, c.post) for c in comments]
Expected:
[(1, u'My first comment', <Post: First Post>), (2, u'My second
comment', None)]
Got:
[(2, u'My second comment', None), (1, u'My first comment', <Post:
First Post>)]
The order in which results are returned is generally not deterministic
with SQL Anywhere unless an ORDER BY clause is used. It appears that
this is in line with what is expected by Django (see:
http://www.djangoproject.com/documentation/models/ordering/).
I can submit a patch that adds ordering information to the affected test
cases, but I first wanted to make sure that this is indeed expected
behaviour for the test suite and not a bug in our backend
implementation. Is this not an issue with any of the other database vendors?
Thanks,
Nathan Auch
Sybase iAnywhere
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django developers" 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-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
