Ok, I'll try.
Carles
El 21/06/2010, a las 19:03, mdipierro <mdipie...@cs.depaul.edu> escribió:
> The only file you need to look into is gluon/contrib/gql.py
>
> specifically the select() function which calls filter returns the Rows
> object
>
> On Jun 21, 11:55 am, Carles Gonzalez <carle...@gmail.com> wrote:
>> Ok, thanks! I would like to make the patch myself, but the innards of
>> web2py are somewhat complex...
>>
>> Thanks again, Carles.
>>
>> On Mon, Jun 21, 2010 at 6:43 PM, mdipierro <mdipie...@cs.depaul.edu> wrote:
>>> Probably it would not be hard to implement. I will look into this next
>>> week but if somebody sends me a patch before that I will take it.
>>
>>> Massimo
>>
>>> On Jun 21, 9:25 am, Carles Gonzalez <carle...@gmail.com> wrote:
>>>> Hi,
>>
>>>> I have developed some applications in web2py, and 2 are running
>>>> currently in gae, but now i have serious problem.
>>
>>>> My current project is a social application, and when i design
>>>> (example) the tables to make an user follow the actions other user
>>>> (twitter like) I find that many-to-many relationships in app-engine
>>>> are not easily supported.
>>
>>>> From my understanding using the tools present in web2py right i would
>>>> need to do a lot of processing in memory, an that would hurt
>>>> performance greatly.
>>
>>>> The pattern proposed by app store developers uses lists and "parent"
>>>> relationship:
>>
>>>> class Message(db.Model):
>>>> sender = db.StringProperty()
>>>> body = db.TextProperty()
>>
>>>> class MessageIndex(db.Model):
>>>> receivers = db.StringListProperty()
>>
>>>> indexes = MessageIndex.all(keys_only = True).filter('receivers = ',
>>>> user_id)
>>>> keys = [k.parent() for k in indexes)
>>>> messages = db.get(keys)
>>
>>>> For using that pattern in web2py I would need a method for specifying
>>>> the parent of a model instance. Can I specify that relationship using
>>>> any method I don't know? If not, would it be hard to implement?
>>
>>>> Thanks in advance!
