Add an interview table to help custom query reports.

[GoogleCodeExporter]

Right now I'm trying to query the answer table for two answers to a survey,
but it's requiring a massive amount ( O(n+1) ) of queries. Though I admit
that I may be missing some Django query trickery that could solve in O(1).

A simple interview table which contains submission_date, interview_uuid,
user_id and session_key while adding an interview_id column to the answer
table would reduce the query count in this case (and also reduce db memory
footprint in general). 

Oh and the possible answers to query are far too numerous to create a
survey for each possibility.

Original issue reported on code.google.com by michael....@gmail.com on 10 Apr 2009 at 6:05

[GoogleCodeExporter]

Delete this Google hiccup please.

Original comment by michael....@gmail.com on 10 Apr 2009 at 6:08

[GoogleCodeExporter]

Original comment by yann.ma...@gmail.com on 11 Apr 2009 at 2:39

• Changed state: Duplicate