No - just 'normal' tables for the moment.
On Thursday, November 29, 2012 11:01:12 AM UTC+4, Andy W wrote:
>
> Can anybody expand on 13.5 of the Web2py Manual on how best to adapt an
> app to run on GAE? In particular, how to do away with linked tables.
>
> For example, I have a simple app that generates a cash receipt. The input
> form displays a dropdown list for the user to select a payment method
> (cash, credit card etc). The allowed payment methods are held in a second
> table, so that users can adapt & extend them.
>
> Using sqlite this is simple to achieve with a linked table. For GAE, I am
> assuming it is better to store the text value ("cash" or "credit card" etc)
> as part of the receipt record, rather than storing the link, but how to
> achieve this?
>
> I have tried reading the payment options in to a list and using this list
> to define allowable entry values:
>
> payment_methods=[p.name for p in db(id>0).select(db.payment_method.name)]
>> db.receipt.paid_by.requires = IS_IN_SET(payment_methods)
>
>
> This works on sqlite, but on GAE gives the error:
>
> File "/Users/andy/www/web2py/gluon/dal.py", line 1414, in get_table
>> raise RuntimeError, "No table selected"
>> RuntimeError: No table selected
>
>
> Any suggestions??
>
--
