Change log for 3.3.15 says:
Many improvements to the test suite. Test coverage now exceeded 98%
What does this mean?
Does it mean that (say) the sqlite3 command line tool (especially the .dump
command) is tested at each release now?
---
I'm asking this because previously on this list it was made clear that the
command line tool was not part of the test suite. The .dump command in that
tool is (very very often!!!) described as a good backup. But it isn't (IMHO).
It's not a tested tool, and indeed, there were 3.x.x releases where that tool
was not correctly dumping out (eg.) triggers.
It just seems that to download sqlite source and know that it contains a
reliable backup tool with it would add to this first rate open source software,
regardless of how simple it might be to write our own code in our language of
choice to dump databases.
Either that or consider removing the .dump command? I say this because I have
seen so very much documentation that references the .dump feature, and yet that
feature lies in code that is (was?) tested very differently than the rest of
sqlite. That just seems uncomfortable...
Backups are so important, etc..
I hope my point is made. I'm not complaining here at all. Trying to be
helpful.
Thanks much in advance,
Trever
---------------------------------
Sucker-punch spam with award-winning protection.
Try the free Yahoo! Mail Beta.
