Litedb: Bugs in v5.

Created on 31 May 2018  Â·  13Comments  Â·  Source: mbdavid/LiteDB

Hi Mauricio.

We have been looking a lot on your v5 branch and we are aware that it's a beta version and therefore not stable, but I'm still asking if you have an estimate on when there will be a stable version of v5?

Best regards
Michael Robdrup
Qualiware

Most helpful comment

Hi @QRobberDK, thanks for your interesting in LiteDB. The new v5 version will not be only an upgrade version from v4, but a complete re-write of LiteDB. This new version uses lot of new features and need create a much more complex structure. Also, LiteDB v5 will not only for embedded apps but will be access via TCP/NamedPipe (with server version). With this, LiteDB will support not only .NET but can be used in any other platform/language.
Current version are in still in complete dev and not work at all. I'm changing almost every day to get best code and performance... and I use 2 computer (home and work), so sometime I commit in github only to access in another one (with not compiling code).
I'm dedication this all this year for this new version... and my plans are release in end of 2018 a stable version of LiteDB.
I will release, in 2 or 3 months the first beta of engine-only database for first public tests.

All 13 comments

Hi @QRobberDK, thanks for your interesting in LiteDB. The new v5 version will not be only an upgrade version from v4, but a complete re-write of LiteDB. This new version uses lot of new features and need create a much more complex structure. Also, LiteDB v5 will not only for embedded apps but will be access via TCP/NamedPipe (with server version). With this, LiteDB will support not only .NET but can be used in any other platform/language.
Current version are in still in complete dev and not work at all. I'm changing almost every day to get best code and performance... and I use 2 computer (home and work), so sometime I commit in github only to access in another one (with not compiling code).
I'm dedication this all this year for this new version... and my plans are release in end of 2018 a stable version of LiteDB.
I will release, in 2 or 3 months the first beta of engine-only database for first public tests.

Hi @mbdavid, is it possible that you can manage to add transaction in 4v it would be nice.

Hi @AwsomeCode, unfortunately is not easy to implement this. When I wrote v4 i removed lots of parts that implement transaction (from v3).

If you can wait, new v5 will be fully support for transaction with snapshot version control and a new window admin UI 😄

image

Oh! this looks nice. Sure I can wait, currently I am using SQLite. As soon as v5 beta comes out I will start testing it out.

Still on 2.04 and been holding off due to lack of transaction support. Although I've had to drop a lot of use of transactions where I can get away with it or work around, due to some issues that only occur in a transaction.

Is v4 considered stable now, and what's the upgrade path from 2.04? Code and more importantly upgrading our customer's database files.

Hi @mbdavid

As I can see, your project is getting bigger, congratulations about it.

After reading this part

Also, LiteDB v5 will not only for embedded apps but will be access via TCP/NamedPipe (with server version)

, a server version, very interesting

Please, add transactions in this version, sometime business logic requires "all or nothing" to be right and avoid corrupted data.

Hi @jboada, yes, transactions are back in v5. Actually, all v5 was around this... write ahead log (WAL) for transaction support.

The server version will not be available at first time because I spend lot of time (much more than I expected) fixing and improving query performance (with support a new SQL language)... so, some features will be delivery later.

How is the first release of v5 progressing?

I have to start a new project I and would like to use LiteDB, but not sure if I should start with v4 or if I should hold out for the first release of v5 if it is close?

If I start with v4, will it be an easy upgrade to v5 or will there be many changes that I would have to make?

Hi @wilberolive, v5 will still under dev because I'm complete change storage engine to get great performance improvement. Current v5 are not as fast as I wanted... and I made bad decisions about BinaryReader and BinaryWriter. I'm fixing this in a new branch.

But you can starts with v4 and migrate after to v5.. API change will be minimal. Datafile format will change too, but I already made import/convert from old version.

Thanks for your reply.

Will the data file upgrade from v4 to v5 be an automated process when connecting to the data file for the first time with v5 or is it a manual process? I ask because I have hundreds of clients each with their own v4 data file. I cannot upgrade the data files for everyone manually. So would like a way to do it automatically via code?

This migration will run at first time open database in v5 (with old-version backup support).

This new version with transactions will be nice and this automatic upgrade
makes it look amazing!

On Fri, 26 Oct 2018, 8:13 p.m. Mauricio David, notifications@github.com
wrote:

This migration will run at first time open database in v5 (with
old-version backup support).

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mbdavid/LiteDB/issues/998#issuecomment-433576948, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACmRjTNKFxF2eq6jdr5CjqN0Wv-yxhkeks5uo6w3gaJpZM4UU9Ad
.

Hi! With the objective of organizing our issues, we are closing old unsolved issues. Please check the latest version of LiteDB and open a new issue if your problem/question/suggestion still applies. Thanks!

Was this page helpful?
0 / 5 - 0 ratings

Related issues

muhamad picture muhamad  Â·  3Comments

dangershony picture dangershony  Â·  3Comments

ghiboz picture ghiboz  Â·  4Comments

furesoft picture furesoft  Â·  4Comments

nightroman picture nightroman  Â·  3Comments