Closed superware closed 5 months ago
I believe so, it had a new release in Feb this year
Personally, I have had nothing but problems with this library. Specifically the "shared" mode and asynchronous code. It's like balancing a single hair on a pin needle, and has lead to complete application deadlocks (try operating this lib in a Quartz background job - aka Real threads, not Parallels), constant random runtime errors (disposed??? what disposed it?), and unreliable operation execution timing (try deleting everything, and reinserting everything - duplicate Id's). And lord save the man who attempt to use it's transaction system. Literally have to run a threaded infinite while() loop to check the counts to "find out" when it's done deleting things. The error codes are generic and unhelpful. And there's no documentation to figure out "why" something isn't working. It's madness; and that is my position on it.
I really want to love this product. But yeah, I had the same question.
Who's in charge of bugs around here anway? Sheesh. 658 open issues is notable to say the least.
Personally I've had far more success with Lucene.Net, highly reliable for at least 5 years so far for me. But Lucene.net is very hard to work with when you're new to it or need advanced "flow patterns" (zero Linq options). Everything does exactly what it says it does, no "black magic", great documentation, backed by years of Apache development (despite being an Alpha/Beta port to C#).
Not trying to be mean. But I wouldn't be here right now if things were working like they should. I don't have time to help fix other people's broken things. Or I would. We need a savior, imo.
It's natural for every open source project to have an instability phase, the issue with LiteDB is that this phase takes too long. I hope @mbdavid will get back to this (and the many PRs) or at least find some other coordinator so the truly wonderful potential will not go to waste.
I’ve not found any open source projects, even large company funded ones, that have good documentation or fix the PR’s efficiently. I recently used AvaloniaUI, had an issue, got told to look elsewhere. This project is great, but lacks documentation and has bugs that stopped me using it.
I think the problem, specifically with this repository, besides the original developer had to re-prioritise other life scenarios, is that it got to a popular and in a cool state, then, instead of focusing on making it great, they added stuff to it like sql syntax.
Actually, we can try using sqlite.
If the author is short of money, I think donations to the project can be opened.
I think the project is all but dead. The last two releases are bug-ridden and encryption weaknesses have not been fixed for years. It's not usable in any serious project. It needs a quick change of direction with more than one person looking after it. @mbdavid has done a great job getting it this far, but it needs support from more than him now to move it forward. There is nothing else like it for C#, and I hope it can survive, but I can't wait on it any longer. I'll be moving all my code to a SQLite version with encryption
In light of recent critical issues and repository activity, is LiteDB still being maintained?