2) I need to write current time to a hash's field (as an object's last
updated timestamp), but TIME is not allowed in writing context. I can use
an external time source, but why on earth is this decision? What
consequence will there be, if we can call TIME in lua scripting?
> 2) I need to write current time to a hash's field (as an object's last
> updated timestamp), but TIME is not allowed in writing context. I can use
> an external time source, but why on earth is this decision? What
> consequence will there be, if we can call TIME in lua scripting?
> Thanks,
> Shannon
> --
> --
> You received this message because you are subscribed to the Google Groups
> "Redis DB" group.
> To post to this group, send email to redis-db@googlegroups.com.
> To unsubscribe from this group, send email to
> redis-db+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/redis-db?hl=en.
About the time, I'm pretty sure that's because of replication. If the time is a parameter it can be replicated, but if the time is read from the OS every time the results will be different. The same thing applies to random parameters.
> 2) I need to write current time to a hash's field (as an object's
> last updated timestamp), but TIME is not allowed in writing
> context. I can use an external time source, but why on earth is
> this decision? What consequence will there be, if we can call TIME
> in lua scripting?
> Thanks,
> Shannon
> --
> -- > You received this message because you are subscribed to the Google
> Groups "Redis DB" group.
> To post to this group, send email to redis-db@googlegroups.com
> <mailto:redis-db@googlegroups.com>.
> To unsubscribe from this group, send email to
> redis-db+unsubscribe@googlegroups.com
> <mailto:redis-db%2Bunsubscribe@googlegroups.com>.
> For more options, visit this group at
> http://groups.google.com/group/redis-db?hl=en.
> -- > You received this message because you are subscribed to the Google > Groups "Redis DB" group.
> To post to this group, send email to redis-db@googlegroups.com.
> To unsubscribe from this group, send email to > redis-db+unsubscribe@googlegroups.com.
> For more options, visit this group at > http://groups.google.com/group/redis-db?hl=en.
I still don't understand why replication is a problem. On the EVAL document
page there is a demo on generating random keys, by calling math.random() in
lua. Since it is "random" why Redis insist that Master and Slave must
hold the same data?
> About the time, I'm pretty sure that's because of replication. If the
> time is a parameter it can be replicated, but if the time is read from the
> OS every time the results will be different. The same thing applies to
> random parameters.
>> 2) I need to write current time to a hash's field (as an object's last
>> updated timestamp), but TIME is not allowed in writing context. I can use
>> an external time source, but why on earth is this decision? What
>> consequence will there be, if we can call TIME in lua scripting?
>> Thanks,
>> Shannon
>> --
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Redis DB" group.
>> To post to this group, send email to redis-db@googlegroups.com.
>> To unsubscribe from this group, send email to
>> redis-db+unsubscribe@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/redis-db?hl=en.
> --
> You received this message because you are subscribed to the Google Groups
> "Redis DB" group.
> To post to this group, send email to redis-db@googlegroups.com.
> To unsubscribe from this group, send email to
> redis-db+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/redis-db?hl=en.
> --
> You received this message because you are subscribed to the Google Groups
> "Redis DB" group.
> To post to this group, send email to redis-db@googlegroups.com.
> To unsubscribe from this group, send email to
> redis-db+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/redis-db?hl=en.