When using MemoryStore, transaction() is undefined about dstore HOT 1 CLOSED

Hi @fedoraniumus,

While transaction() is a documented method that can be present on a store, none of the stores in the dstore package implement it. It is simply presented as an option for those who need transaction support on a store.

It looks like we need to improve how our documentation speaks about Collection and Store. We use "Collection" and "Store" to describe different aspects of an object store.

A Collection represents a list of items and the query that produces the list of items. When you create an instance of dstore/Memory, that instance is a Collection of all items in the store. When you call filter() on that instance, a Collection is returned representing the list of items resulting from the filter operation. However, the only way the Collection's items are exposed is through the return value of the fetch or fetchRange methods or by using the forEach method.

A Store is a Collection that also includes the ability to get, add, put, and remove individual objects. When you call filter on a Memory store, the resulting object is both a Collection and a Store. It is a Collection representing the filter query, and it is a Store in that it exposes methods for retrieving, creating, updating, and removing objects from the entire store. This provides a useful encapsulation where collection consumers receive a single object representing a query and, when available, the ability to add, update, and remove items from the store.

Does that help?

from dstore.