-
Notifications
You must be signed in to change notification settings - Fork 9
fix: incorporate cross space transaction API #1281
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
| } | ||
| export interface INotFoundError extends Error {} | ||
| export type IStorageTransactionProgress = Variant<{ | ||
| open: IStorageTransactionLog; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
clarification: to entries move from open to pending to done?
if i want to know all, no matter the status (as scheduler needs it), should it iterate over all of them? who else is going to call this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Idea has being that they all contain same transaction log, it's just transaction itself is either open, pending or done. In the implementation I renamed open to edit to make it more clear that transaction is editable while when pending or done it's no longer editable.
Summary by cubic
Added support for cross-space transactions in the storage interface, allowing transactions to read from multiple memory spaces and write to one.
readerandwritermethods for accessing different memory spaces within a transaction.