Using System.Data.SQLite from the new site
-
Anyone has managed to use the latest System.Data.SQLite? The original site http://sqlite.phxsoftware.com/[^] now redirects to a new site. The trouble is that the new site is very austere, it describes itself as Fossil, sadly this is a well chosen name. There is no setup file to download like before, only source. Building is more complicated that it looks and the documentation is at best hard to follow. I am starting to wonder now whether it is a good think or not that the project went open source. Puzzled.
-
Anyone has managed to use the latest System.Data.SQLite? The original site http://sqlite.phxsoftware.com/[^] now redirects to a new site. The trouble is that the new site is very austere, it describes itself as Fossil, sadly this is a well chosen name. There is no setup file to download like before, only source. Building is more complicated that it looks and the documentation is at best hard to follow. I am starting to wonder now whether it is a good think or not that the project went open source. Puzzled.
As far as I see it seems that there's somekind of transition going on (http://system.data.sqlite.org/index.html/doc/trunk/www/index.wiki[^]). Based on the info on the downloads page new versions should become available in the future. Another site that has the SQLite ADO provider is http://sourceforge.net/projects/sqlite-dotnet2/[^]. Have you tried downloading from there?
The need to optimize rises from a bad design.My articles[^]
-
As far as I see it seems that there's somekind of transition going on (http://system.data.sqlite.org/index.html/doc/trunk/www/index.wiki[^]). Based on the info on the downloads page new versions should become available in the future. Another site that has the SQLite ADO provider is http://sourceforge.net/projects/sqlite-dotnet2/[^]. Have you tried downloading from there?
The need to optimize rises from a bad design.My articles[^]
Indeed, this is probably a transition issue. In the meantime it is frustrating for users that can't, don't have the time or simply don't know how to compile C++. I was sort of hoping by posting here to find someone that had done it already. I thought the other site was complete other implementation. You're right I could go for it, the risk in all of this would be to go for a project that won't be maintained in the future. Do you think this project is better?
-
Indeed, this is probably a transition issue. In the meantime it is frustrating for users that can't, don't have the time or simply don't know how to compile C++. I was sort of hoping by posting here to find someone that had done it already. I thought the other site was complete other implementation. You're right I could go for it, the risk in all of this would be to go for a project that won't be maintained in the future. Do you think this project is better?
I'm sorry to say but I haven't used SQLite for ages so my current knowledge is mainly out-of-date. But I guess that if you design the db interface well, changing the library afterwards won't be so big issue. Most likely this means that you would create different kind of wrappers for db operations, such as a common method for executing a command or querying the db etc. This way you won't have so many places to change if the library is changed.
The need to optimize rises from a bad design.My articles[^]
-
I'm sorry to say but I haven't used SQLite for ages so my current knowledge is mainly out-of-date. But I guess that if you design the db interface well, changing the library afterwards won't be so big issue. Most likely this means that you would create different kind of wrappers for db operations, such as a common method for executing a command or querying the db etc. This way you won't have so many places to change if the library is changed.
The need to optimize rises from a bad design.My articles[^]
I have had to give up on the broken official version and I have my own version here: https://github.com/PaulS/SQLiteDotNetProvider It has most of the code changes from the official version, but will still build. (There are almost no changes.) Their version has missing files, and won't build an install. It's really about the same as 1.0.66, but compiles with sqlite 3.7.5. When the official version is working again I would probably go with that.