Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upGitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
WIP: Added event persistence implementation for StreamsDb #676
Conversation
|
|
rasmus
changed the title
|
The tests should as a minimum use |
|
@promontis First of all, thanks for making the effort to write an event store implementation on top of StreamsDB. Very much appreciated! I've created a pull request that introduces the test project in your fork. This test project is based on the suggestion of @rasmus (thanks for the awesome test set!). The pull request also has some fixes. If you accept my pull request on your fork, you can test drive the StreamsDB event store in your project. My pull request updates your develop branch, since EventFlow uses that branch as the trunk. So I would suggest you update this pull request to reflect that change. See: promontis#1 |
|
The are still 3 things left to do:
|
Added CursorsStream to ReadModuleUpdate poco Working test, but still need to add transaction when psa is done
@pjvds could you review and add a test