On Oct 26, 5:25 am, Jonathan Lundell jlund...@pobox.com wrote:
On Oct 25, 2011, at 2:06 PM, Pawel Jasinski wrote:
hi,
thanks! That solved my ~ problem.
Unfortunately for my öäü (chars above 128 and below 255 in latin-1) I
still need to overcome 2 challenges:
1. re.U must be supplied
hi all,
I have discovered that args in url are restricted to ascii.
In addition tilde (~) is also not considered valid in arguments.
I am using rest mapping @request.restful() where as far as I can tell
there is no technical reason to restrict args (RFC 3986).
I also found similar limitation for
hi,
of directory traversal attacks (~ specifically).
how exactly?
I am talking about arguments and only arguments.
I agree that ~ in case of application/controller/method makes no sense
In case of static agree 100%, but that is different control path.
The arguments are just that, arguments. If
. Is it acceptable?
2. at some point before match call args have to be subjected to
decode('utf-8') to become unicode
Any suggestions?
--Pawel
On Oct 25, 9:18 pm, Jonathan Lundell jlund...@pobox.com wrote:
On Oct 25, 2011, at 11:57 AM, Pawel Jasinski pawel.jasin...@gmail.com wrote:
hi,
of directory
hi,
it is cosmetic, but can be a pain for someone no so familiar with
python.
In examples for restful api:
def index():
def GET(*args,**vars):
patterns = [
/persons[person],
/{person.name.startswith},
/{person.name}/:field,
, it is cosmetic. I believe it is a bad idea to give variable
a name which matches name of the build-in function
cheers,
pawel
On Thu, Jun 9, 2011 at 3:26 PM, Massimo Di Pierro
massimo.dipie...@gmail.com wrote:
I do not understand. :-(
On Jun 9, 3:21 am, Pawel Jasinski pawel.jasin...@gmail.com
),
db.third.on(db.third.r13_first_id==db.first.id),
db.fourth.on(db.fourth.r14_second_id==db.second.id),
])
On Apr 28, 2:22 pm, Pawel Jasinski pawel.jasin...@gmail.com wrote:
hi,
this appears to be an old issue already discussed and marked as
solved:http://groups.google.com/group/web2py
hi,
short update
I could use executesql, but is there an easy way to reconnect the
result of executesql into the rows returned by db(...).select(...)?
As a work around I do the following:
0. modify DAL so select( ) accepts extra parameter to overwrite
generated sql
1. develop and test with
,db.fourth.ALL,
left= [
db.second.on(db.first.id==db.second.r12_first_id),
db.third.on(db.third.r13_first_id==db.first.id),
db.fourth.on(db.fourth.r14_second_id==db.second.id),
])
On Apr 28, 2:22 pm, Pawel Jasinski pawel.jasin...@gmail.com wrote:
hi,
this appears to be an old issue already
hi,
this appears to be an old issue already discussed and marked as
solved:
http://groups.google.com/group/web2py/browse_thread/thread/d7f5e5820176813/4d990c3c7475c48b
http://groups.google.com/group/web2py/browse_thread/thread/f4ef82fd34371863/8e7a741d676cea6e
but, I got it again :-(
Here is my
Hi,
I just hit the same problem and can reproduce in trivial case
in model:
db.define_table('foo', Field('x'))
db.define_table('bar', Field('label'), Field('ref',db.foo))
in controller:
def insertone():
id=db.foo.insert(x=xxx)
db.bar.insert(label=label,ref=id)
def index():
=accepted
return dict(form=form)
On Jan 26, 10:37 am, Pawel Jasinski pawel.jasin...@gmail.com wrote:
Hi,
I just hit the same problem and can reproduce in trivial case
in model:
db.define_table('foo', Field('x'))
db.define_table('bar', Field('label'), Field('ref',db.foo
Hi,
Are you sure you want the form readonly?
Yes
What if you remove readonly?
The 'None' changes into drop down with ids or whatever is in the
format argument of the field.
If you want readonly you do not need accepts
Good point, changed. It does not help with the main problem.
I also have
hi,
when I try to put multiple forms generated with SQLFORM.factory things
act a bit odd.
#controller
def index():
form1 = SQLFORM.factory(Field('a'))
if form1.accepts(request.vars, session) :
print form1 accepted
form2 = SQLFORM.factory(Field('b'))
if
14 matches
Mail list logo
