Constrain keys
Rather than supporting any() - constrain at least to binary()/integer() or string().
This commit is contained in:
parent
50967438d3
commit
bde188e691
3 changed files with 7 additions and 11 deletions
|
@ -458,10 +458,7 @@ get_nextbucket(NextBucket, NextKey, Tag, LedgerSnapshot, BKList, {C, L}) ->
|
|||
leveled_codec:next_key(K)
|
||||
end,
|
||||
get_nextbucket(B, NK, Tag, LedgerSnapshot, BKList, {C, L})
|
||||
end;
|
||||
{NB, _V} ->
|
||||
leveled_log:log("B0010",[NB]),
|
||||
[]
|
||||
end
|
||||
end.
|
||||
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue