hi Steve for me you are absolutely right and this is the sintuation in sqlite3explorer. with a simple rename (the old one), copy & rename of the DLL you can deal with any of the sqlite issues! regards, e.
Цитат на писмо от Steve O'Hara <[EMAIL PROTECTED]>: > Hi Ralf, > > SqliteSpy is a nice tool but this is a weakness, not a > strength - we > used to call this sort of thing "built-in obsolescence". > Woudn't it be > better for you if you didn't have to track changes made > by Richard to > the engine? > This is also a problem with quite a few of the wrappers > that embed the > engine. > > Just a thought, > > Steve > > > -----Original Message----- > From: > [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > org] On Behalf Of Ralf Junker > Sent: 03 February 2006 10:12 > To: sqlite-users@sqlite.org > Subject: [RBL] Re: [sqlite] ANN: SQLiteSpy 1.5.1 released > > Hello Joe Wilson, > > the build-in database engine is a much praised feature of > SQLiteSpy. It > simplifies the life of many users, and mine as well, > since there can be > no incompatabilities with wrong DLLs and versions. > > I am sorry that you can not use SQLiteSpy with your > custom DLL. Maybe > you would like to contribute your changes to the SQLite > sources, so they > can become part of SQLite and SQLiteSpy as well? > > Apart from that, I monitor the development of SQLite > closely and will > always update SQLiteSpy to the latest version of SQLite > as quickly as > possible. > > Regards, > > Ralf > > >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. > > > > >
