Home/ Questions/Q 7191951
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-28T19:50:12+00:00

I have a pure-SQL queryset: SELECT ft2.user_id, avg(…) figure, count(…) as figure_count FROM figures_table

  • 0

I have a pure-SQL queryset:

SELECT ft2.user_id, avg(...) figure, count(...) as figure_count
FROM figures_table ft,
     figures_table ft2
WHERE ft.user_id=%(current)s AND
      ft.user_id != ft2.user_id AND
      ft2.user_id IN (%(others)s)
GROUP BY ft2.user_id

I want to make another one:

SELECT %(id)s as id,
       avg(figure * figure_count) figure
FROM (%(subquery)s) subquery

Where %(subquery)s is the first query. When I try doing commands like

User.objects.raw(second_query, {'subquery': first_qs.query})

it raises exceptions: can't adapt type QuerySet. Passing a string also doesn’t work, as it becomes quoted in the resulting query. Should I just format the string with the nested query?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Should I just format the string with the nested query?

    Yes.

    That’s essentially what raw SQL is for.

    It’s complaining because you are trying to put SQL in a variable parameter slot, and the db adapter doesnt know how to do that. (in fact, in other circumstances, what you are doing would be a SQL-injection attack, and is exactly the sort of thing that parameterized queries are designed to prevent)

    Just use regular string formatting operations to join your queries, and use that as the source for your next raw queryset.

    (do remember to escape any “%” characters in your SQL, if you are using python string interpolation on them, though)

    • 0