On Wed, Oct 28, 2009 at 2:01 PM, leszek <[email protected]> wrote: > > But you can accomplish it in more simple way. It is many-to-many > relationships. > Simple have entity USER and ITEM and USER-ITEM entity keeping both > keys. If there exists USER-ITEM entity having both keys than user read > this item, if not than opposite. This way you can avoid this > limitation. okay... the good old cross tables ;) in fact that's how I implement it now, but imho the Sets thing would be much cleaner.
But: Brett Slatkin talks in http://www.youtube.com/watch?v=AgaL6NGpkB8 about Sets (or Lists) that contain all recepients to deal with the "I can solve the Twitter scaling problem". Does this mean that everything explained in Brett's talk about this issue is nice in theory, but in reality not really possible due to quotas and such? Would be not really cool.... Thanks, Raphael > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en -~----------~----~----~----~------~----~------~--~---
