Closed GoogleCodeExporter closed 9 years ago
In that last example consider "source" an SQL query
Original comment by kruk...@gmail.com
on 20 Apr 2010 at 2:49
Now it's not possible at all to create empty aggregate objects... so it can't
be done by design :)
Original comment by anti...@gmail.com
on 26 Apr 2010 at 6:34
Original comment by anti...@gmail.com
on 27 Aug 2010 at 11:23
This is obnoxoius. An empty set is *different* from a non-existent one.
Consider { x | x < 10 and x > 11 } vs the { x | x is an element of the set of
keys I haven't cached yet }.
Original comment by cpf...@valetude.com
on 23 Sep 2014 at 5:14
How, specifically, is the behaviour of an existing but empty set different from
a nonexistent set that behaves as though it is empty?
You can of course check key existence if desired, or you could add a dummy
sentinel value. But I confess to not being very clear on how it is "obnoxious".
Your example doesn't clarify it, IMO.
Original comment by marc.gravell
on 23 Sep 2014 at 5:24
This google code project is not in use anymore. Please report bugs to
https://github.com/antirez/redis.
Also I'm not even sure I get your point with the examples. If you want to
discuss this further try asking on the mailing list or in the IRC channel.
Original comment by jeredi...@gmail.com
on 23 Sep 2014 at 5:25
Original issue reported on code.google.com by
kruk...@gmail.com
on 20 Apr 2010 at 2:47