No, that just changes how the DAL checks for conflicts with reserved SQL words.
It depends on the backend which words are problematic. See the book. If you
really want to use a reserved word check out the rname parameter of Field.
Nico de Groot
--
Resources:
- http://web2py.com
- http://web2p
Hi!
I found the _next-parameter to become an array during login and I wonder if
this is a feature and if I'm using it "the right way(tm)".
Situation is as follows:
def user():
import logging
logging.warn('default/user _next={}'.format(request.vars._next))
return dict(form=auth(), ne
Sry, forgot to mention: Ubuntu Linux Ubuntu 14.04.5 LTS with
web2py 2.15.2-stable
--
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 mess
The Auth login method adds _next as a hidden input in the login form, so
_next ends up in both request.get_vars and request.post_vars. Because
request.vars combines get_vars and post_vars and each of those includes a
"_next" key, request.vars ends up with _next being a list including the
values
Reading your answer I realize, that I'm not doing it "the right way" :)
I don't know when I added the next-parameter to the return value, but that
was clearly a mistake. I'll remove it and try again!
Many thanks for your answer,
Silvan
--
Resources:
- http://web2py.com
- http://web2py.com/book
I think I misunderstood your answer the first time I read it.
Am Freitag, 27. Oktober 2017 15:39:33 UTC+2 schrieb Anthony:
>
> The Auth login method adds _next as a hidden input in the login form, so
> _next ends up in both request.get_vars and request.post_vars. Because
> request.vars combines
Hello i'm blocked so i need your opinion
I have many groups of Objects.
Each group has some fields.
Each field has 3 functions: visible,init and disabled.
I'm coding something like
main.py
from all_fields import *
all_fields.py
Class Load_fields:
def f1():
this field should have
This is my best shot...
It works but as it can have for example 30 groups of fields it may not be
the simplest/smartest code
class Group1_fields(object):
def __init__(self, fields):
print "calling init"
self.fields = fields
class f1(object):
def __init__(self, visible,disa
Hi Stifan
Earlier this year web2py started to quote all SQL entities and this caused
a problem for Firebird because this DB creates entities in uppercase by
default.
Anyhow, it may help if you change your DAL declaration to use switches:
ignore_field_case,
entity_quoting
DAL('firebird://SYS
Wow, thanks!
The rname parameter of Field solved the problem.
2017-10-27 6:14 GMT-02:00 Nico de Groot :
> No, that just changes how the DAL checks for conflicts with reserved SQL
> words. It depends on the backend which words are problematic. See the book.
> If you really want to use a reserved
my second shotsmaller code i omitted the 3rd function "init"
as in the first shot...
class Group1_disabled:
def f1(self):
print "f1 disabled"
def f2(self):
print "f2 disabled"
class Group1_visible:
def f1(self):
print "f1 visible"
def f2(self):
here book description from
http://web2py.com/books/default/chapter/29/04/the-core#cache :
Note, time_expire is used to compare the current time with the time the
requested object was last saved in the cache. It does not affect future
requests. This enables time_expire to be set dynamically when
On Thursday, October 26, 2017 at 7:26:48 AM UTC-7, Anthony wrote:
>
> There's no need to select the extra record and then drop it via Python.
> Instead you can just change the range of the limitby tuple to get exactly
> the records you want.
>
>
Perhaps the issue is not knowing how many recor
thanks villas, after modified the dal parameter DAL(..., ignore_field_case
= True, entity_quoting = False, ...), theres a lot of thing deal with
auth_user in firebird:
e.g.
1. deal with auth_user password field (already posted above)
auth.settings.password_field = 'password2'
auth.define_tables(u
14 matches
Mail list logo
