On Wed, Feb 3, 2010 at 1:46 PM, Kenneth Gonsalves <law...@au-kbc.org> wrote:
> On Wednesday 03 Feb 2010 10:09:44 am Russell Keith-Magee wrote:
>> > Exception Type: NameError at /
>> > Exception Value: global name 'query' is not defined
>>
>> This isn't the same problem that you originally reported. This
>> particular problem was logged as #12732, and fixed in [12359].
>
> this problem occurs for me from the reported revision and is still occuring
> with the latest svn - 12377, and as I said the error messages differ depending
> on the page loaded. I have copied the error message occuring in latest svn
> using the test setup which I have posted in another post on this thread.
>>
>> I would also note that you previously said that the problem was
>> between [12200] and [12300] - why are you reporting [12352] as the
>> problem revision?
>>
>
> yesterday I was in panic mode - I kept going downwards until I got a revision
> that worked - which was 12200. 12300 did not work, but I did not test it
> thoroughly. Today, on thorough testing of 12300, it did work, and I zeroed in
> on 12352. I have not tested all the revisions between 12352 and current trunk,
> but all those I have tested did not work. The traceback on admin for my test
> site is here:
Ok - seriously - if you want help debugging this, you need to get your
story straight.
You have now reported 3 completely different stack traces.
Your initial report gave this stack trace:
-------------------------
django/db/backends/postgresql/base.py", line 57, in execute
return self.cursor.execute(sql, params)
TypeError: argument 1 must be str, not unicode
-------------------------
You are yet to provide the revision and conditions under which this bug occurs.
Your second report gave this stack trace:
-------------------------
File "/usr/lib/python2.6/django/db/backends/postgresql/base.py" in execute
57. return self.cursor.execute(query, args)
Exception Type: NameError at /
Exception Value: global name 'query' is not defined
-------------------------
This is the problem reported as #12732, and fixed in [12359]. Any
attempt to use a revision between [12352] and [12359] will fail with
this error if you're using the postgres database backend.
In your most recent report, you describe the following:
-------------------------
File "/usr/lib/python2.6/django/db/backends/postgresql/base.py" in execute
57. return self.cursor.execute(sql, params)
Exception Type: DatabaseError at /admin/
Exception Value: ERROR: syntax error at or near "11"
LINE 1: ... AND "django_session"."expire_date" > 2010-02-03 11:10:34.2...
^
-------------------------
You say that this problem occurs on the current trunk, but you haven't
said what I have to do to reproduce this problem.
Which of these problems are you *actually* having? And please, don't
rush to answering. I really do want to help you identify the cause of
this problem - especially if it has been caused by a recent commit -
but my patience for wading through inconsistent bug reports is
limited. At some point, I will give up and declare the problem
'worksforme'.
Yours,
Russ Magee %-)
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-us...@googlegroups.com.
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
