We do something similar in a different context. I don't know if our way is necessarily better, but it would work like this:
1. add a field to campaign called something like enteredUsers 2. once a user adds a campaign, update the campaign, adding a value unique to that user to enteredUsers 3. the negation can now be done by excluding the user's unique id from the enteredUsers field, instead of excluding all the user's campaigns The downside is it will increase the number of your commits, which may or may not be OK. Rachel On 2/13/08, alexander lind <[EMAIL PROTECTED]> wrote: > Hi all > > Say that I have a solr index with 5000 documents, each representing a > campaign that users of my site can join. The user can search and find > these campaigns in various ways, which is not a problem, but once a > user has found a campaign and joined it, I don't want that campaign to > ever show up again for that particular user. > > After a while, a user can have built up a list of say 200 campaigns > that he has joined, and hence should never see in any search results > again. > > I know this functionality could be achieved by simply building a > longer and longer negation query negating all the campaigns that a > user already has joined. I would assume that this would become slow > and ineffective eventually. > > My question is: is there a better way to do this? > > Thanks > Alec >
