[web2py] Re: GAE issue with !=

2010-12-09 Thread howesc
it works, and the != test that i tried also works. i wonder if it has to do with how i tested the constuction? my test was of a dynamic query built like: def build_query(field, op, value): """ Builds the web2py query object for a given field """ if op == 'equals': return field == value elif op ==

[web2py] Re: GAE issue with !=

2010-12-08 Thread mdipierro
Please give it one more try. On Dec 8, 5:42 pm, howesc wrote: > actually, not the same issue, different error, same line. :(

[web2py] Re: GAE issue with !=

2010-12-08 Thread howesc
actually, not the same issue, different error, same line. :(

[web2py] Re: GAE issue with !=

2010-12-08 Thread howesc
hmm, same issue: ERROR 2010-12-08 23:38:06,535 restricted.py:151] Traceback (most recent call last): File "/home/cfhowes/tools/web2py_src/web2py/gluon/restricted.py", line 188, in restricted exec ccode in environment File "/home/cfhowes/tools/web2py_src/web2py/applications/pump/controllers/defaul

[web2py] Re: GAE issue with !=

2010-12-08 Thread mdipierro
Please try again. You do not need to copy dal.py over sql.py. As of yesterday they are the same in trunk. Massimo On Dec 8, 4:13 pm, howesc wrote: > i just pulled from trunk, copied dal.py to sql.py, and did not get past > logging in to my app to test for you. i got this error: > > ERROR 2010-12

[web2py] Re: GAE issue with !=

2010-12-08 Thread howesc
i just pulled from trunk, copied dal.py to sql.py, and did not get past logging in to my app to test for you. i got this error: ERROR 2010-12-08 22:09:31,819 restricted.py:151] Traceback (most recent call last): File "/home/cfhowes/tools/web2py_src/web2py/gluon/restricted.py", line 188, in restric

[web2py] Re: GAE issue with !=

2010-12-07 Thread mdipierro
does the new dal work for you? On Dec 7, 6:46 pm, howesc wrote: > i am using it.  just tested it out on an application that is running > web2py 1.85.3, which is a bit outdated i suppose. > > do keep in mind that if the value is not set, it will fail all > comparisons, so you must set a default va

[web2py] Re: GAE issue with !=

2010-12-07 Thread howesc
i am using it. just tested it out on an application that is running web2py 1.85.3, which is a bit outdated i suppose. do keep in mind that if the value is not set, it will fail all comparisons, so you must set a default value on any fields that you want to use in a comparison. christian On Dec