a few questions: Isn't the plan to do away with gql.py?
Does the query class encapsulate sql or is it a different syntax? (I know I'm being lazy here I will look it up) On Feb 1, 10:29 pm, Robin B <robi...@gmail.com> wrote: > Yes it is ignored. > > Some of the tests were copied from sql.py, and there is lots of left > over baggage in gql.py from sql.py. > > gql.py once, as its name implies, generated GQL, but now gql.py uses > Google's Query class to build queries (cleaner and faster). > > The SQL stuff will be removed very soon. > > Robin > > On Feb 1, 3:52 pm, billf <billferr...@blueyonder.co.uk> wrote: > > > There are loads of examples of GAE define_tables that include > > migrate='something.table' (including the doctests in gql.py) but, as > > far as I can see, no code in gql.py that processes migrate=. > > > Am I correct in thinking that for GAE this clause is just ignored? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---