Re: [sqlite] ANN: SQLiteSpy 1.5.1 released
On 2/3/06, Joe Wilson <[EMAIL PROTECTED]> wrote: > I commonly swap different sqlite3.dll versions in and out > between runs while using Mike Cariotoglou's (excellent) > SqliteExplorer and have no difficulty at all. I'm not sure > why others have such problems will DLLs. DRH does a good job testing and ensuring compatibility. A certain large company whose products I have to work with regularly makes decisions for financial reasons instead of technical ones. For them incompatible old versions help them sell you more software. ;)
Re: [sqlite] ANN: SQLiteSpy 1.5.1 released
That's great! Looking forward to it. --- Ralf Junker <[EMAIL PROTECTED]> wrote: > Hello Joe Wilson, > > I want to thank you and everybody else to share their thoughts on SQLiteSpy > and let you know > that I very much value your feedback. I initially wrote SQLiteSpy for my own > personal needs > only, but it has since then certainly improved thanks to the responses I have > received by many > of its users. > > The recent disusion on the internal / external database issue made me realize > that there is > indeed a need for an internal database as well as an external DLL support for > SQLiteSpy. I hope > to be able to cater for both needs by keeping the internal SQLite engine plus > adding optional > support dynamically linking the SQLite3.dll in a future release. However, a > requirement will be > that all custom DLLs be interface-compatible with the latest original > sqlite3.dll for SQLiteSpy > to function properly. > > If you have further suggestions (appart from in-grid-editing - this is > already on the list ;-)), > please let me know! > > Regards, > > Ralf > > >But I guess the number of satisfied users of the statically-linked > >SQLiteSpy outnumber the users requiring a custom/older/newer > >sqlite3.dll DLL by 100 to 1, so it's my loss. :-) __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: [sqlite] ANN: SQLiteSpy 1.5.1 released
Hello Joe Wilson, I want to thank you and everybody else to share their thoughts on SQLiteSpy and let you know that I very much value your feedback. I initially wrote SQLiteSpy for my own personal needs only, but it has since then certainly improved thanks to the responses I have received by many of its users. The recent disusion on the internal / external database issue made me realize that there is indeed a need for an internal database as well as an external DLL support for SQLiteSpy. I hope to be able to cater for both needs by keeping the internal SQLite engine plus adding optional support dynamically linking the SQLite3.dll in a future release. However, a requirement will be that all custom DLLs be interface-compatible with the latest original sqlite3.dll for SQLiteSpy to function properly. If you have further suggestions (appart from in-grid-editing - this is already on the list ;-)), please let me know! Regards, Ralf >But I guess the number of satisfied users of the statically-linked >SQLiteSpy outnumber the users requiring a custom/older/newer >sqlite3.dll DLL by 100 to 1, so it's my loss. :-)
Re: [sqlite] ANN: SQLiteSpy 1.5.1 released
In general there are advantages and disadvantages about static linking of dll's. Major advantage is that if it works, you don't have to bother about dll's. But if you have more app's using the database then it might be a disadvantage. I like to use same version with all my apps and use a central dll. Another disadvantage is that if there is a bug in the dll everbody must wait for a new release and download. Otherwise the dll is immediately available. It might be a good option to support both. Use your static linking but allow the external dll to be used. THis is best of both worlds. albert Quoting Joe Wilson <[EMAIL PROTECTED]>: My dozen or so custom SQLite functions are not useful to anyone else, as they are very specific to my application's data. (Never mind the fact that they would not be accepted by DRH anyway). I commonly swap different sqlite3.dll versions in and out between runs while using Mike Cariotoglou's (excellent) SqliteExplorer and have no difficulty at all. I'm not sure why others have such problems will DLLs. But I guess the number of satisfied users of the statically-linked SQLiteSpy outnumber the users requiring a custom/older/newer sqlite3.dll DLL by 100 to 1, so it's my loss. :-) --- Ralf Junker <[EMAIL PROTECTED]> wrote: 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. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: [sqlite] ANN: SQLiteSpy 1.5.1 released
Hi , Can I download SQLiteSpy some other link. It seems my ISP has some issues connecting to the site. Much better if someone can e-mail me SQLiteSpy straight away. Thanks in advance. Regards, Vishal Kashyap http://vishal.net.in On 2/2/06, Ralf Junker <[EMAIL PROTECTED]> wrote: > Hello, > > the new SQLiteSpy 1.5.1 has just been released. SQLiteSpy is a single-exe > database manager for SQLite with the complete SQLite library already build > in. SQLiteSpy is the ideal tool for developers as well as customers who want > to explore the insides of their SQLite databases. > > SQLiteSpy is Freeware. You can download it from > > http://www.yunqa.de/delphi/sqlitespy/ > > The new version updates the internal database engine to SQLite 3.3.3 and > includes the following improvements: > > * Attached databases now show up in the schema tree view, including all their > tables, indexes, views and triggers. > > * New File -> Attach Database... menu item. > > * Attached databases can be easily detached using the schema tree view's > context menu. > > * ALTER TABLE ... ADD COLUMN automatically updates the schema tree view. The > schema tree view should now automatically adjust to any internal change to > the database schema. > > * Executing an SQL statement which does not return any data now shows all > columns on top of an empty result grid. This change was requested by many > users who felt confused when the grid was not cleared if no results were > returned. > > Best Regards, > > Ralf > > -- With Best Regards, Vishal Kashyap. http://www.vishal.net.in
Re: [sqlite] ANN: SQLiteSpy 1.5.1 released
My dozen or so custom SQLite functions are not useful to anyone else, as they are very specific to my application's data. (Never mind the fact that they would not be accepted by DRH anyway). I commonly swap different sqlite3.dll versions in and out between runs while using Mike Cariotoglou's (excellent) SqliteExplorer and have no difficulty at all. I'm not sure why others have such problems will DLLs. But I guess the number of satisfied users of the statically-linked SQLiteSpy outnumber the users requiring a custom/older/newer sqlite3.dll DLL by 100 to 1, so it's my loss. :-) --- Ralf Junker <[EMAIL PROTECTED]> wrote: > 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. > > __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: [sqlite] ANN: SQLiteSpy 1.5.1 released
Whether to use an external DLL or have the functionality embedded? I have a both-ways compromise. I store a copy of the DLL inside the app as a resource. Then if the DLL doesn't extst in the app dir I copy the DLL out, but this also allows me to update the DLL to something more recent by replacing just the DLL. As for using a common sqlite.dll with a whole pile of 3rd party application - I wouldn't take the risk for all the reason already mentioned. This is probably not the nicest solution, but my customers tend to be "zero-install" sort of people - ie copy the application to another machine and hope for the best, so I like an application that looks after itself. Regards, Carl.
Re: [sqlite] RE: [RBL] Re: [sqlite] ANN: SQLiteSpy 1.5.1 released
For a tool to be thoughtfully designed to remove DLL HELL is a great strength, not a weakness. Tools should be robust and reliable and work when all else is failing, and Sqlitespy is in that genre. Steve O'Hara wrote: 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.
Re: [sqlite] RE: [RBL] Re: [sqlite] ANN: SQLiteSpy 1.5.1 released
- Original Message - From: "Steve O'Hara" <[EMAIL PROTECTED]> 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. Unfortunately not all of us have an option. Here's some examples from my own experiences from incorporating a wrapper for SQLite in .NET: - The Compact .NET Framework can't pass 64-bit numbers by value, only 32-bit ... so all functions that require a double or an int64 have to be wrapped by another C function that takes pointers to those values instead, and then forwards the dereference to the actual SQLite call. - The CF also cannot call cdecl functions, all API calls in a DLL must be stdcall. So every API function in sqlite has to be wrapped with a stdcall version which forwards to the cdecl version. - The .NET framework (both full and CF) cannot pass cdecl callback function pointers. All callback functions must be stdcall, so again, all callbacks have to be wrapped. - Many folks have added encryption support to the library, including me. Mine is specific to the Windows platform (it was my way of adding encryption and yet not invalidating DRH's paid package). None of these changes merit merging with the core sqlite codebase, yet all are required in order to have a fully-functioning .NET provider for SQLite. Robert
Re: [sqlite] RE: [RBL] Re: [sqlite] ANN: SQLiteSpy 1.5.1 released
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. > > > > >
[sqlite] RE: [RBL] Re: [sqlite] ANN: SQLiteSpy 1.5.1 released
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.
Re: [sqlite] ANN: SQLiteSpy 1.5.1 released
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
RE: [sqlite] ANN: SQLiteSpy 1.5.1 released
> -Original Message- > From: Ralf Junker [mailto:[EMAIL PROTECTED] > Sent: 03 February 2006 10:12 > To: sqlite-users@sqlite.org > Subject: Re: [sqlite] ANN: SQLiteSpy 1.5.1 released > 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? This isn't a good answer. The problem is that if everyone added their favourite custom functions etc to the SQLite source it would become bloated and lose part of its appeal. I much prefer keeping the SQLite DLL external. Tim Read my tech blog: http://www.itwriting.com/blog
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.
Re: [sqlite] ANN: SQLiteSpy 1.5.1 released
Hello Ken & Deb Allen, >Cool. When will you release a MacOS X version? There will be no native MacOS X version of SQLiteSpy, I'm afraid. SQLiteSpy delveloped for Win32 only, but maybe there are ways to run Win32 executables on MacOS X, like it is possible with Linux using the Wine Windows Emulation layer? Regards, Ralf
Re: [sqlite] ANN: SQLiteSpy 1.5.1 released
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. --- Ralf Junker <[EMAIL PROTECTED]> wrote: > Hello, > > the new SQLiteSpy 1.5.1 has just been released. SQLiteSpy is a single-exe > database manager for > SQLite with the complete SQLite library already build in. SQLiteSpy is the > ideal tool for > developers as well as customers who want to explore the insides of their > SQLite databases. > > SQLiteSpy is Freeware. You can download it from > > http://www.yunqa.de/delphi/sqlitespy/ > > The new version updates the internal database engine to SQLite 3.3.3 and > includes the following > improvements: > > * Attached databases now show up in the schema tree view, including all their > tables, indexes, > views and triggers. > > * New File -> Attach Database... menu item. > > * Attached databases can be easily detached using the schema tree view's > context menu. > > * ALTER TABLE ... ADD COLUMN automatically updates the schema tree view. The > schema tree view > should now automatically adjust to any internal change to the database schema. > > * Executing an SQL statement which does not return any data now shows all > columns on top of an > empty result grid. This change was requested by many users who felt confused > when the grid was > not cleared if no results were returned. > > Best Regards, > > Ralf > > __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: [sqlite] ANN: SQLiteSpy 1.5.1 released
Cool. When will you release a MacOS X version? -ken On 2-Feb-06, at 7:58 AM, Ralf Junker wrote: Hello, the new SQLiteSpy 1.5.1 has just been released. SQLiteSpy is a single-exe database manager for SQLite with the complete SQLite library already build in. SQLiteSpy is the ideal tool for developers as well as customers who want to explore the insides of their SQLite databases. SQLiteSpy is Freeware. You can download it from http://www.yunqa.de/delphi/sqlitespy/ The new version updates the internal database engine to SQLite 3.3.3 and includes the following improvements: * Attached databases now show up in the schema tree view, including all their tables, indexes, views and triggers. * New File -> Attach Database... menu item. * Attached databases can be easily detached using the schema tree view's context menu. * ALTER TABLE ... ADD COLUMN automatically updates the schema tree view. The schema tree view should now automatically adjust to any internal change to the database schema. * Executing an SQL statement which does not return any data now shows all columns on top of an empty result grid. This change was requested by many users who felt confused when the grid was not cleared if no results were returned. Best Regards, Ralf
Re: [sqlite] ANN: SQLiteSpy 1.5.1 released
Congratulations on a stylish and very handy product. Ralf Junker wrote: Hello, the new SQLiteSpy 1.5.1 has just been released. SQLiteSpy is a single-exe database manager for SQLite with the complete SQLite library already build in. SQLiteSpy is the ideal tool for developers as well as customers who want to explore the insides of their SQLite databases. SQLiteSpy is Freeware. You can download it from http://www.yunqa.de/delphi/sqlitespy/ The new version updates the internal database engine to SQLite 3.3.3 and includes the following improvements: * Attached databases now show up in the schema tree view, including all their tables, indexes, views and triggers. * New File -> Attach Database... menu item. * Attached databases can be easily detached using the schema tree view's context menu. * ALTER TABLE ... ADD COLUMN automatically updates the schema tree view. The schema tree view should now automatically adjust to any internal change to the database schema. * Executing an SQL statement which does not return any data now shows all columns on top of an empty result grid. This change was requested by many users who felt confused when the grid was not cleared if no results were returned. Best Regards, Ralf
