web2py default IDs are integers. we have some GAE users who are using named keys....or at least i added support for named keys on GAE based on some user's requests.
i don't have a generic solution for the DAL that chunks belongs queries in groups of 30, so it is still left as something the user must do. as i come across spots in the web2py core that use belongs i've been making those functions chunk in groups of 30 when the datastore is GAE. i'm undecided anyway if this should be automatic for users or if they should be forced to realize that large belongs queries are implemented as multiple datastore calls on GAE. cfh On Saturday, September 15, 2012 11:15:57 AM UTC-7, Alan Etkin wrote: > > your patch does the correction in the DAL - i almost suggested the same >> thing (and since i was working off of 2.0.8 at the time that's why i missed >> your change). though i think it is possible to have key fields in GAE that >> are not ints so i was hesitant to make the change in the DAL myself. > > > I didn't take that on account. Anyway, web2py integer ids should always be > integers. No? > > >> either way, my patch also breaks the belongs into groups of 30 since on >> GAE any given belongs can't have more than 30 (and i use multiselects with >> much more than 30) >> >> > Yes, I saw it after posting. Will then be possible to use .belongs with > more than 30 references? > --
