Last modified: 2013-06-18 15:26:44 UTC
INSERT INTO archive (ar_namespace,ar_title,ar_comment,ar_user,ar_user_text,ar_timestamp,ar_minor_edit,ar_rev_id,ar_text_id,ar_text,ar_flags,ar_len,ar_page_id,ar_deleted) SELECT page_namespace,page_title,rev_comment,rev_user,rev_user_text,rev_timestamp,rev_minor_edit,rev_id,rev_text_id,'','',rev_len,page_id,rev_deleted FROM page,revision WHERE page_id = '3040' AND (page_id = rev_page)
not enough information to reproduce.
As tstarling said, missed that the sqlite maintainer was the one who opened this and gave it to himself.
Yes, I should have given more details. This bug was just a quick note to myself, while doing something else. Error 19: column ar_len is not unique. Doesn't happen at all times, does not happen frequently. I was able to reproduce it consistently on one page, but it vanished after I edited it. The bug is pretty critical when deleting files, because SQL error at that time does not lead to rollback of non-database changes, such as move of file to archive storage. Page deletion seems to fail gracefully.
(In reply to comment #3) > The bug is pretty critical when deleting files, because SQL error at that time does > not lead to rollback of non-database changes, such as move of file to archive > storage. Page deletion seems to fail gracefully. > That's related to bug 17560 and its friend bug 19751.
WINDOWS RESTORE AND SQL RECOWER SOFTWEAR INSTROL THEN RECOWER AFTER UPDATE SQL
Downgrading severity, it can't result in data loss now.
Unassigning default assignments. http://article.gmane.org/gmane.science.linguistics.wikipedia.technical/54734
Can't repro any longer, closing pending more reports.