Opened 16 years ago
Closed 16 years ago
#11664 closed (invalid)
Invalid SQL is generated as part of the aggregation unit tests
| Reported by: | egenix_viktor | Owned by: | nobody |
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | 1.1 |
| Severity: | Keywords: | ||
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
The following Django 1.1 unit tests seem to generate invalid SQL: aggregation, aggregation_regress. It happens even if I run then on SQLite.
The generated SQL always contains a strange GROUP BY clause, like this:
GROUP BY aggregation_book, aggregation_book, aggregation_book, aggregation_book, aggregation_book, aggregation_book, aggregation_book, aggregation_book, aggregation_book
The table name varies with the actual unit test. It happens several times.
Change History (2)
comment:1 by , 16 years ago
comment:2 by , 16 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
I've printed out the SQL from every single call in those functions and this isn't happening. Closing for now. Please reopen if you have a step-by-step set of instructions to reproduce, but the above would imply that aggregation was broken and it wouldn't even execute (the database would complain). That isn't the case, so I think it's a problem on the reporter's side.
Note:
See TracTickets
for help on using tickets.
We're going to need some more information here, as I am absolutely unable to reproduce.