| 1 | | I totally understand that column references can be ambiguous, but we convert these Django queries into SQL and inject them into raw sql, so it's a major overhaul for us to have to convert all the Django queries to raw sql because of this change. We do use `values` and/or `values_list`, but it still doesn't preserve the column names. Even with an `order_by` and `values` combination, same result. If there is another way we can force the Django ORM to preserver these column names, please advise. |
| | 1 | I totally understand that column references can be ambiguous, but we convert these Django queries into SQL and inject them into raw sql, so it's a major overhaul for us to have to convert all the Django queries to raw sql because of this change. We do use `values` and/or `values_list`, but it still doesn't preserve the column names. Even with an `order_by` and `values` combination, same result. If there is another way we can force the Django ORM to preserve these column names, please advise. |