Opened 16 years ago

Closed 15 years ago

Last modified 13 years ago

#9407 closed (invalid)

The testModerationQueueContents test case does not work on databases without a microsecond precision datetime data type

Reported by: egenix_viktor Owned by: nobody
Component: Database layer (models, ORM) Version: 1.0
Severity: Keywords: MSSQL microsecond datetime ordering
Cc: Triage Stage: Accepted
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no


Database server: MS SQL Server 2005

Unit test: regressiontests/moderation_view_tests

Test case: ModerationQueueTests.testModerationQueueContents

Statement: self.assertEqual(list(response.context[0]["comments"]), [c1, c2])

The test fails due to wrong row order, since list(response.context[0]["comments"]) gives [c2, c1] instead of [c1, c2].

The SQL query generated (split into multiple lines for readability):

FROM [django_comments]
WHERE ([django_comments].[is_public] = %s AND
       [django_comments].[is_removed] = %s )
ORDER BY [django_comments].[submit_date] ASC


(False, False)

Which will be translated to (0, 0).

The above test case depends on sorting the comments on their submit_date. Since MS SQL does not have a microsecond component in its datetime columns both comments are inserted with the same submit_date value with nearly 100% probability. It might cause a result set with unexpected record order, since the above query sorts the rows on a column containing identical values, therefore no sort order defined at all.

So, this bug is due to the lack of microsecond precision of MS SQL Server's datetime data type. However, it works on SQLite, since SQLite can store the microseconds as well.

The test case should be modified to insert the test data with different submit_date values or sort on the primary key as well as a secondary ordering.

Change History (5)

comment:1 by egenix_viktor, 16 years ago

It is actually in `regressiontests/comment_tests/tests/moderation_view_tests'.

comment:2 by Jacob, 15 years ago

milestone: 1.1
Triage Stage: UnreviewedAccepted

comment:3 by Jacob, 15 years ago

milestone: 1.11.2

Punting to 1.2: we don't officially support MSSQL (yet) so this'll have to wait.

comment:4 by Travis Cline <travis.cline@…>, 15 years ago

Resolution: invalid
Status: newclosed

The offending test was removed in r11639. Marking as invalid

comment:5 by Jacob, 13 years ago

milestone: 1.2

Milestone 1.2 deleted

Note: See TracTickets for help on using tickets.
Back to Top