Sphene Community Tools

Yes, i'm see it
Updating thread information for test1
done updating thread information.
saved post / threadinformation: ThreadInformation object
[02/Feb/2008 16:17:39] "POST /forums/post/1/ HTTP/1.1" 302 0

weird.. but you still see no 'last post' in the list of threads ?

could you again look into the table sphboard_threadinformation and paste me an example of a result to a query like: SELECT * FROM sphboard_threadinformation WHERE root_post_id = ... using some existing post id ..

mysql> SELECT * FROM sphboard_threadinformation WHERE root_post_id = 1;
+----+--------------+-------------+-------------+------+---------------------+--
------------+----------------+------------+------------+------------------------
+
| id | root_post_id | category_id | thread_type | heat | heat_calculated | s
ticky_value | latest_post_id | post_count | view_count | thread_latest_postdate
|
+----+--------------+-------------+-------------+------+---------------------+--
------------+----------------+------------+------------+------------------------
+
| 1 | 1 | 1 | 1 | -90 | 2008-02-02 15:50:13 |
0 | 1 | 1 | 3 | 2008-02-02 15:50:08
|
+----+--------------+-------------+-------------+------+---------------------+--
------------+----------------+------------+------------+------------------------
+
1 row in set (0.05 sec)

could you try the following setting:

SPH_SETTINGS['workaround_select_related_bug'] = True

it sounds like a similar problem.. but afaik this should already be fixed in django trunk .. but anyway .. it's worth a try ..

ok .. it seems my memory wasn't correct.. the bug is still not fixed in django trunk .. i just couldn't reproduce it because the default communitydraft settings file .. does indeed set this option:

from settings_local.py.tmpl:

# The workaround_select_related_bug is currently required in django trunk.
# See http://code.djangoproject.com/ticket/4789 (If this patch was committed,
# or you applied the patch manually you can disable this workaround to improve
# performance)
SPH_SETTINGS['workaround_select_related_bug'] = True

don't ask me why this simple patch wasn't applied yet in django..

Worked. Thanks for support!

FYI: this has been fixed in the latest SVN trunk.