At 04:21 03/02/2006, you wrote:
SQLiteSpy is a very nice looking application.
I'm not sure if this is a good feature, though:
Built in SQLite Engine
SQLiteSpy comes as a single file executable with
the SQLite database engine already build into the
application. There is no need to distribute any DLLs,
which makes SQLiteSpy easy to deploy with customers.
I have a custom sqlite3.dll so I would not be able
to use my databases with your app. Nor would your
users be able to upgrade to newer versions of
sqlite3.dll.
It's a good feature for me. I dislike the .dll and .so inferno. Some
apps which use different versions of sqlite3 (3.1.x and 3.3.x) can
install different .so or .dll, overlapping or installing different
versions along directory tree and brain headhache, for me. So for a
problem-less environment i (and some others too) end copying the
.so or .dll in the application directory. Doing so is a bit...
ridiculous, create the lib, open the lib, close the lib, call the
lib, and it's slower. Better, embed SQLite in your app. Perhaps i
must upgrade the app when new SQLite appears, usually it's only click
rebuild. On the other hand if i install an app which install the last
SQLite .so/.dll and has a nasty bug, all app i use with SQLite will
fail, perhaps corrupting the database. For some code, making a
external lib is a good choice, for SQLite... i prefer embed it in my code.
-------------------------------------------------------------------------------------------
Useful Acronymous : DMCA = Don't Make Content Accessible