HN Explorer

11 comments

[ 5.4 ms ] story [ 51.4 ms ] thread
lemcoe9
This does not seem like a good idea. Redis does not serve the same use-cases that MySQL aims to.
famousactress
Isn't that a supremely plausible reason for wanting to move data from one to the other? If everything was working out just great in MySQL there'd probably be no reason to move it :)
twerquie
The point of the post is how to efficiently port data from MySQL to Redis once you have decided to make the switch. It's not making any recommendations on when or why to use Redis.
ipedrazas
I guess this is exactly the point of moving some data out of the MySQL, right?

Different use-cases, different systems.

firefoxman1
Does anyone else wish that Redis had a disk-based version? Other key/value stores like Riak are nice, but I want the simplicity, commands, and raw data types of Redis in a version that could handle terabytes of data. But maybe I'm the only one that wants that.
[deleted]
(comment deleted)
babuskov
I believe this could all be done with a single CONCAT. Looks like author is unaware that you can CONCAT(param1, param2, param3, ..., paramN)
meritt
It could also be done without a sub-table either

    select concat("*4\r\n$4\r\nHSET\r\n$15\r\nevents_all_time\r\n$", length(action), "\r\n", action, "\r\n$", length(`count`), "\r\n", `count`, "\r") from events_all_time
twerquie
Good point, I removed the nested CONCATs for clarity. Thanks!