search

ramsenthil18 / elmah

Automatically exported from code.google.com/p/elmah
Apache License 2.0
0 stars 0 forks source link

Use of C#-SQLite library #262

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What new or enhanced feature are you proposing?

Using the csharp-sqlite library instead of the existing library.  C#-Sqlite is 
written in C# and is 100% compatible with SQLite (according to the unit tests). 
 It's SQLite written in C#.

http://code.google.com/p/csharp-sqlite/

I'd be more than happy to make this change.

What goal would this enhancement help you achieve?

It removes the dependence on a 32-bit or 64-bit SQLite DLL.  After all, isn't 
platform independence one of the reasons we use C#?  Dealing with the 32/64 bit 
issue is a pain when deploying across that barrier.

The downside is perhaps the code will go stale.  This isn't much of an issue 
since this is a risk even with the existing library.  In fact, the existing one 
did go dormant until SQLite took over maintenance.  There was even talk about 
it using the C#-SQLite library instead of the SQLite DLLs.

Original issue reported on code.google.com by masil...@gmail.com on 5 Dec 2011 at 5:44

GoogleCodeExporter commented 8 years ago 
According to the project FAQ[1], it is not considred ready for prime time:

Q: Is this ready for prime time? 
A: Don't know -- let me know what you think 

Perhaps that's a tongue-in-cheek? 

> I'd be more than happy to make this change.

Why not clone the ELMAH Sandbox and add an ErrorLog implementation there on top 
of C#-SQLite? This has three benefits. One, we don't have to worry about 
immediate risks. Two, it can be field tested, and three, you can start to 
contributing right away.

[1] http://code.google.com/p/csharp-sqlite/wiki/FrequentlyAskedQuestions
[2] http://code.google.com/p/elmah-sandbox/

Original comment by azizatif on 18 Dec 2011 at 3:28

GoogleCodeExporter commented 8 years ago 
This issue has been migrated to:
https://github.com/elmah/Elmah/issues/262
The conversation continues there.
DO NOT post any further comments to the issue tracker on Google Code as it is 
shutting down.
You can also just subscribe to the issue on GitHub to receive notifications of 
any further development.

Original comment by azizatif on 25 Aug 2015 at 8:21