I had the same kind of problems when I started with django. My problem was
the tracebacks wanted to include the full contents of any QuerySet variables
I had in my functions, and that just wasn't going to work given they
sometimes had more than >500,000 rows. I "fixed" it by putting my QuerySet
v
On 3/1/07, Tim Chase <[EMAIL PROTECTED]> wrote:
...
> the
> tracebacks seem to want to try and pull back some humongous
> portion of data (600k+ records in one table, and this is the
> "small" testing DB).
Those variables are somewhere in your call stack. The traceback
doesn't "want to" do it.
I've encountered an odd problem that I'm hoping someone out there
has encountered and can offer tips.
I've got a fairly gargantuan database of phone information (my
company manages cell-phone accounts for other companies).
However, when I try to troubleshoot my views/templates, the
tracebacks
3 matches
Mail list logo
