Liz Steel wrote:
Sorry to keep on about this, but I raised a ticket on Tuesday (number
981) with severity and priority of 1 (since this is a major issue for my
projet) and I haven't heard anything back yet.
Even if it is not going to be fixed, I really need to know, as then we
can take some other action with this.
Ticket #981 will not likely be fixed anytime soon because:
* The description is vague and gives us little
clue of how to reproduce the problem.
* The ticket is against version 2.8.13. 2.8.15 is current.
* There is no mention of what operating system is being used.
* There is no example source code.
* There is no example SQL code.
* No patches or suggested changes are included.
* The contact information is a hotmail account from someone
we do not know.
Here are ways that you can increase the probability of getting
a bug fixed:
* Describe what operating system, programming language, and
execution environment the problem occurs in.
* Provide sample program source code and/or sample SQL code
that reproduces the problem. The smaller the sample the
better.
* Describe what to do in order to reproduce the problem,
including examples.
* Report bugs against the latest version of SQLite. Bugs
against version 3.0.8 or CVSHEAD are fixed first. Then
bugs against 2.8.15. Anything else gets a lower priority.
* Provide suggest patches.
* Provide contact information that tells us something about
who you are. People using SQLite in high-use open-source
projects get priority handling.
* Purchase a professional support agreement as described at
http://www.hwaci.com/sw/sqlite/prosupport.html. Support
customers always get priority bug handling. This is the
best way for commercial users to get bugs fixed faster.
--
D. Richard Hipp -- [EMAIL PROTECTED] -- 704.948.4565
