Sorry, I don't understand this line. although I belive storing records without id assignment would be > restrictive for apps
Do you mean web2py apps or GAE apps? What did you mean by "restrictive" (and I doubt it will be actually compatible at all Compatible with what? Sure, when you would insert using a key_name, and without an numeric id, the will be web2py API functionalities that wont work anymore. (the ones that expect a numeric id returned) But you would know that you don't need those functionalities if you would decide to use a key_name. On Wednesday, January 8, 2014 3:52:18 PM UTC+1, Alan Etkin wrote: > > > But does that mean you should not allow it to be inserted that way? > > Nothing restricts users from operating (using web2py api) on rows > inserted with GAE api.... > > There's no restriction on the use of the datastore, since it is not a > service reserved for web2py apps, although I belive storing records without > id assignment would be restrictive for apps (and I doubt it will be > actually compatible at all, with the exception of the keyed tables > mentioned before, in case it is supported). > > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
