Why do you have to define all headers? I would only want to display the
headers to those columns that I define in the columns list but now it
requires me to set headers to every other column too that I'm not showing.
That is stupid
On Friday, 8 July 2011 04:17:39 UTC+2, ニコノコ wrote:
Nope, I'm
This is a great option but what is the best practice then to have the
represents-functionality still on board? It is a bit messy to do that
totally on your own
On Friday, 30 November 2007 16:26:12 UTC+1, mdipierro wrote:
What you try to do is too much personalization for sqltable. You
When has this behaviour changed? I can't seem to find it on log
On Jun 17, 7:33 pm, Jose jjac...@gmail.com wrote:
On 17 jun, 11:35, Anthony abasta...@gmail.com wrote:
On Friday, June 17, 2011 10:16:16 AM UTC-4, Jose wrote:
Hi,
In later versions of the trunk the default view
(name,string),
Field(parent, reference tags,default=None),
format=%(name)s)
On Jun 1, 9:30 am, Oskari oskari.pe...@gmail.com wrote:
Hi,
I'm reporting a possible bug with trunk version of dal.py. I'm having
the traceback:
Traceback (most recent call last):
File /home
Hi,
I'm reporting a possible bug with trunk version of dal.py. I'm having
the traceback:
Traceback (most recent call last):
File /home/www-data/web2py/gluon/restricted.py, line 184, in
restricted
exec ccode in environment
File /home/www-data/web2py/applications/backend/controllers/
Hi,
I'm writing doctests to my application. Most of my functions are
decorated with @auth.requires_login().
Running doctests through the web IDE runs the tests in a different
environment depending on if I'm logged in in the app.
What kind of pattern is here meant to be used to test logged-in
I'm still struggling with the IS_IN_DB-validator. This problem occurs
when trying to implement reference id for example via a controller
line:
request.vars.reftableid = 2
The form just informs it isn't in the database. Why is that?
On Feb 13, 3:14 pm, Oskari oskari.pe...@gmail.com wrote
instead of accountID. I read
somewhere that some databases have case sensitive fields and that
web2py makes some assumptions about this. Just better to work all in
lowercase and avoid hitting that possible complication in the
future. :)
Regards, D
On Feb 16, 6:47 pm, Oskari oskari.pe
someone should be able to spot something obvious -- these bugs
can be right under our noses sometimes :)
-D
On Feb 12, 11:03 pm, Oskari oskari.pe...@gmail.com wrote:
Thank you for your answer villas!
I don't think that is the problem. I am able to make inserts through
Hi!
I'm having trouble making an insert with form.accepts()
Currently I have a custom auth_user that has one extra field:
Field('accountID', db.accounts) with
custom_auth_table.accountID.requires = IS_IN_DB(db,db.accounts.id,id)
While trying to modify variables it fails with not found in db
, but the 3rd attrib of 'IS_IN_DB' doesn't look right?
Maybe if you tried something like this, e.g.
custom_auth_table.accountID.requires = IS_IN_DB(db,db.accounts.id,'%
(name)s')
On Feb 12, 1:28 pm, Oskari oskari.pe...@gmail.com wrote:
Hi!
I'm having trouble making an insert
Hi!
I'm building a SOAP interface with web2py. How can I return an array
with that? I'm guessing its something like:
@service.soap(test,args={},returns={'response':array}
but that isn't recognised as a type. Any ideas?
12 matches
Mail list logo
