bigs
bigs
i'm definitely not against this—i think it could be quite useful. i think we'll need to update datastores that don't natively support this to provide it or at least heavily...
if we want to stay in line with leveldb and descendants, it should happen after the sort. it feels like the semantics of the alternative would almost be undefined On...
yeah, i'm into it. we could even implement a member method, `Prefix(string)` that configures this for you. this definitely increases the power of datastores.
i think the `[Start, Stop)` are a bit more reasonable, even if they require a little extra legwork for the `Prefix` case. that's not a particularly strong feeling, however, so...
my thinking was that if `Start` and `Stop` were still performing prefix matching, `["/a", "/a"]` would be equivalent to `{Prefix: "/a"}`. i do agree, however, that exclusive upper bounds are,...
Yeah, this seems pretty solid. I just kind of wonder if it breaks the facade of our interface altogether... Without generics you're going to have to have a direct reference...
i'd push to have it's semantics not be transactional, i.e. writes in a `Batch` are not guaranteed to happen in the same iota of time. i'd say early flush is...
absolutely!
@hsanjuan @Stebalien Would this have a special API (i.e. `DialSelf`) or do we want to be able to dial our own peer ID? Perhaps we make an option for the...