Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Redis DB
Home
+ new post
About this group
Join this group
Message from discussion why isn't it possible to join two lists in redis or: redis list as a black hole
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Dvir Volk  
View profile  
 More options Feb 20 2012, 5:16 pm
From: Dvir Volk <d...@doat.com>
Date: Tue, 21 Feb 2012 00:16:28 +0200
Local: Mon, Feb 20 2012 5:16 pm
Subject: Re: why isn't it possible to join two lists in redis or: redis list as a black hole
Print | View thread | Show original | Report this message | Find messages by this author

actually, LCONCAT isn't such a bad idea IMHO. surely it shouldn't be worse
than SUNION.
BTW, maybe it's just me, but do most people here use lists for anything
much other than BLPOP and friends?

On Tue, Feb 21, 2012 at 12:05 AM, Josiah Carlson
<josiah.carl...@gmail.com>wrote:

> On Mon, Feb 20, 2012 at 11:37 AM, Oren Dobzinski <ore...@gmail.com> wrote:
> > Joining 2 lists together sounds like a basic and useful operation. Why
> > isn't it supported in redis? what about adding elements of a set or a
> > sorted set to a list or other inter data structure operations? I know
> > it's possible to iterate over the elements of a data structure and add
> > them one by one, but it won't help me since I'm doing these operations
> > on the redis side, inside a big pipeline by using the S*STORE
> > operations.

> I don't know for sure, but part of me thinks it's likely because
> moving or copying data from one structure to another requires a large
> enough set of (source type, destination type) pairs that it didn't
> seem reasonable to implement them all. With scripting, you can likely
> do almost everything that you wanted to do, but if it runs long, it
> will get killed.

> > Whenever I need to SORT anything it needs to go into a list, which is
> > sort of a data black hole, since I can't continue doing other
> > operations on that list without reading elements from the list on the
> > client side.

> You can also sort sets, fetch data from keys and hashes during sorts.

> Regards,
>  - Josiah

> --
> 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.

--
Dvir Volk
System Architect, The Everything Project (formerly DoAT)
http://everything.me

 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google