<h2>How To Report Bugs Against SQLite</h2>
We used to allow anonymous users to enter new bug reports
directly into our bug tracking system. However, our experience
with this procedure was unsatisfactory. Most of the bug reports
we received were of low quality. Many problems turned out to be
problems in the application or in the programmer's mental model
of how SQLite works.
Other "bug reports" were thinly veiled support requests.
Still other reports are so poorly written that we could not figure
out what the problem is. There were also numerous duplicates.
Ideally, our bug database should be usable as an historical reference
to track real problems with SQLite and to facilitate studies of
bug density and software quality. But the high volume of "noise"
reports inhibits that goal.
In effort to reduce the level of background noise, we are now asking
anonymous users to report bugs to the SQLite mailing list. Make sure you check the [http://www.sqlite.org/src/reportlist | existing bug list] first. To report
a bug, please send email to
[mailto:firstname.lastname@example.org | email@example.com].
Email to this list from non-members will be held for review and may take
a day or more to appear on the list. To expedite your message,
sign up for the mailing list at
Non-members can follow the mailing list at
In order for your bug report or request for help to be clearly understood by the people that can help the most, please follow these guidelines:
<li><a href="http://www.chiark.greenend.org.uk/~sgtatham/bugs.html">How to report bugs effectively</a>
<li><a href="http://catb.org/~esr/faqs/smart-questions.html">How to ask smart questions</a>
The idea is that bug reports can be filtered on the mailing list and
those that are actual new bugs can be transferred into our bug tracking
system by registered developers. Anonymous users can continue to
append comments to existing bugs, just not create new bugs.
Thank you for your understanding and cooperation.