STSdb W4.0 RC3 build3 has been released

[a.todorov]

STSdb W4.0 RC3 build3, a new version of the .NET database has been released. This is a bug fixed release.

Release updates:

• bug fixed: StorageEngine.Commit() does not flush the system & user data (thanks: unruledboy)
• changed: STSdb.FromStream() is now public

Download:
STSdb W4.0 RC3 build3

Getting Started:
Getting Started rev.2013-07-11

[unruledboy]

Will the nullable support be there before 4.0 final?

When can we have a more in-depth documentation about the architecture, waterfall-index etc?

For example, so far we only have a few sentences and graphs about the waterfall index, but how exactly it works, why exactly it is a lot faster than other b-tree solutions?

[k.dimova]

When can we have a more in-depth documentation about the architecture, waterfall-index etc?

For example, so far we only have a few sentences and graphs about the waterfall index, but how exactly it works, why exactly it is a lot faster than other b-tree solutions?

We are working on it as we speak. By the end of the day, we will post "Organization of Waterfall Tree". In the next few days, there are going to be detailed examples of how the algorithm works. After that we will add "Maintenance of Waterfall Tree". Finally we are going to post the mathematical analysis.

We should have all the information posted in a week or so.

[unruledboy]

We are working on it as we speak. By the end of the day, we will post "Organization of Waterfall Tree". In the next few days, there are going to be detailed examples of how the algorithm works. After that we will add "Maintenance of Waterfall Tree". Finally we are going to post the mathematical analysis.

We should have all the information posted in a week or so.

really looking forward to it. thanks for the great job.

[k.dimova]

You can find the "Organization of Waterfall Tree" page here.

The "Detailed Examples" page will be added soon.

[unruledboy]

nice. although as it says, there is no secret with source code, but rather than diving into the code straight away, it's better to have an overview, then explanation, and in-depth analysis.