Closed jhellerstein closed 13 years ago
This seems like a nice-to-have, but I don't think it is crucial for 0.0.4.
BTW, making the storage options a modifier to table
doesn't seem quite right to me: whether a given collection is stored persistently or not seems like an important point, not something we want to hide in the option hash. I could see a "stored table" or "persistent table" collection type that takes the storage type as an option, though.
TODO: rename table
to a new name for in-memory collections, make table impl an option.
added sync
as a collection type with a storage engine modifier.
Rather than having separate collection types for each storage engine, we should have a modifier to table that declares the storage engine -- and any of its options in a hash.