New issue 256 by goo...@obry.net: Retry SQL commands if it fails
http://code.google.com/p/vision2pixels/issues/detail?id=256
Some commands seems to fail randomly. Would be nice to add a retry (2 or 3
times) and to log the failing command in a hope to detect a pattern and
better understand what is going on.
Example:
Default_Callback HTML exception for URI="/" EXNAME="DB.DB_ERROR"
EXMESS="DB_Error on Execute INSERT INTO remember_user
('user_login', 'cookie_content') VALUES
('turbo', 'c8a47d49b6658e37342daae51f9aa918')"
Default_Callback HTML exception for URI="/forum/entry" EXNAME="DB.DB_ERROR"
EXMESS="DB_Error on Execute INSERT OR REPLACE INTO last_user_visit
('user_login', 'post_id', 'last_comment_id') VALUES ('turbo', 1870, (SELECT
COALESCE ((SELECT last_comment_id FROM post WHERE id= 1870), 1))"
This last SQL request is not there anymore since the change on the way the
last_user_visit is handled.
Default_Callback HTML exception for URI="/forum/threads"
EXNAME="DB.DB_ERROR" EXMESS="DB_Error on Execute INSERT OR REPLACE INTO
last_forum_visit ('user_login', 'forum_id', 'last_post_id') VALUES
('turbo', 1, (SELECT post.id FROM post, category WHERE
post.category_id=category.id AND c"
Comment #5 on issue 256 by TurboClic: Retry SQL commands if it fails
UPDATE post SET visit_counter=visit_counter+1 WHERE id=1869
Comment #8 on issue 256 by olivier.ramonat: Retry SQL commands if it fails
http://code.google.com/p/vision2pixels/issues/detail?id=256
(No comment was entered for this change.)
I'm able to reproduce the problem easily in gnadelite. Will fix it.
Really good! If the fix is safe we should consider it for 3.3.
Comment #11 on issue 256 by olivier.ramonat: Retry SQL commands if it fails
http://code.google.com/p/vision2pixels/issues/detail?id=256
New gnadelite release (v2.1) fixes the problem. I think this should go in
the 3.3 release.