WIP: In memory database handle #206
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Thanks to that, one can still use custom id based on the event data
Moved creation of db by location to construction
E2E tests were failing, as there was no nested database folder in the 'testing' subdirectory. Probably locally it was created, but git is not commiting empty folders. Adjusted not to require such nesting. Fixed also TS config to compile SQLite package correctly, as some entries were missing. After that fixed the common errors. Added a helper withConnection to streamline the connection management. Now it also uses correctly close in finalize, instead of double closing in case of error. Renamed location to fileName to follow the SQLite naming convention, made it also optional with fallback to in memory. Removed absolute file path and custom, as it won't allow easily passing the filenames without casting that are not typed manually.
…issing .spec in the file name
Thanks to that processors will be automatically typed by that. This can be useful if we have multiple processors for the same stream subscription. It's optional and falls back to event, so each processor can still have it's own event type (e.g. when subscribing to all events). Other option is to put a union of all events in consumer and then use just a subset of those types in processors.
By accident, there was a leftover forcing user to still provide even empty object, which doesn't make sense as it should be passed.
Added also first draft of PostgreSQL async projection processor
… instead of separated method
…low to inject it in the processor
This is the first step to enable message storing and workflows
…dded message kind column
The overview page provided users with a map to navigate the documentation while it keeps growing. As systematic approach the Diataxis framework is introduced.
|
This PR was broken because I made a git mistake, correct one is to be found in the next one -> #207 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR introduces the first iteration of in memory database that is more compatible with Pongo, than the first tries. It is supposed to be the 3rd step from the issue: #179