You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, metall prevents to open the same datastore as read-write twice at the same time.
However, it allows to open a datastore as read-write even if it is already opened in read-only mode.
This causes issues/corruption when the read-writer actually writes. Metall should prevent this.
The desired behaviour would be, allow either:
exactly one read-writer, no one else
many readers, but no read-writer
Small snippet to reproduce:
{ // create datastore
metall::manager mgr{metall::create_only, path};
}
metall::manager mgr_ro{metall::open_read_only, path};
metall::manager mgr_rw{metall::open_only, path}; // this should fail
The text was updated successfully, but these errors were encountered:
Currently, metall prevents to open the same datastore as read-write twice at the same time.
However, it allows to open a datastore as read-write even if it is already opened in read-only mode.
This causes issues/corruption when the read-writer actually writes. Metall should prevent this.
The desired behaviour would be, allow either:
Small snippet to reproduce:
The text was updated successfully, but these errors were encountered: