• antirez's avatar
    Geo: fix edge case return values for uniformity. · 913070a9
    antirez authored
    There were two cases outlined in issue #3512 and PR #3551 where
    the Geo API returned unexpected results: empty strings where NULL
    replies were expected, or a single null reply where an array was
    expected. This violates the Redis principle that Redis replies for
    existing keys or elements should be indistinguishable.
    
    This is technically an API breakage so will be merged only into 4.0 and
    specified in the changelog in the list of breaking compatibilities, even
    if it is not very likely that actual code will be affected, hopefully,
    since with the past behavior basically there was to acconut for *both*
    the possibilities, and the new behavior is always one of the two, but
    in a consistent way.
    913070a9
geo.c 28.7 KB