>
>
> Thanks Anthony,
>
auth.id_group takes the *name* (not id) of a role stored in the
db.auth_group table and returns the id of that role. was so useful.
This worked for me
def add_user_membership(form):
group_id=form.vars.group_name
user_id=form.vars.id
auth.add_membership(gro
Thank you man! you help me <3
2016-11-29 2:35 GMT-02:00 Anthony :
> On Monday, November 28, 2016 at 10:22:53 PM UTC-5, Áureo Dias Neto wrote:
>>
>> Friend, it worked perfectly! thank you!
>>
>> Now, I want to do the inverse of this query, ie select vehicles from the
>> vehicles table, which have
Yes- it looks very bad. I think the below method will work. (Let me know if
you need any elaboration)
rofields = [db..field1, .]
hidden = {}
for f in rofields:
fname = str(f).split('.')[1]
hidden[fname] = r[fname]
form1 = SQLFORM(db., record= , showid=True, hidden=hidden)
for f in rofields:
I was going to download the lib pycopg2 to use postgres on web2py, but
reading the doc and seeing the server it shows that it already has a drive
for postgres that comes with web2py, but when I give a pg8000 import it
does not find the module Which would have to be a package and not an app
mod
Hey guys,
I currently have the following:
db.define_table('bursary_users',
Field('forename', type='string', requires=IS_NOT_EMPTY()),
Field('surname', type='string', requires=IS_NOT_EMPTY()),
Field('studentId', type='string', requires=IS_NOT_EMPTY()
gluon.contrib.pg8000 and gluon.contrib.pymysql
Anthony
On Tuesday, November 29, 2016 at 9:09:38 AM UTC-5, Marlysson Silva wrote:
>
>
> I was going to download the lib pycopg2 to use postgres on web2py, but
> reading the doc and seeing the server it shows that it already has a drive
> for postgr
I have a site written in web2py, spinjazz.net. It works fine. I have bought
an ssl certificate for the site, which works. However when I access the
site via https, it appears as a text only site. I am sure there is a simple
explanation for this, but I do not know what it is.
Any ideas?
Thanks
Try look in link reference css files.. put https maybe..
Em terça-feira, 29 de novembro de 2016 12:47:37 UTC-3, peter escreveu:
>
> I have a site written in web2py, spinjazz.net. It works fine. I have
> bought an ssl certificate for the site, which works. However when I access
> the site via htt
I wonder whether there is a validator on auth_membership user_id and
group_id
I found that I can add the same membership multiple times which is not what
I want.
Kind regards,
Annet
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py
On Tuesday, November 29, 2016 at 8:52:07 AM UTC-5, Sundar wrote:
>
> Yes- it looks very bad. I think the below method will work. (Let me know
> if you need any elaboration)
>
> rofields = [db..field1, .]
> hidden = {}
> for f in rofields:
> fname = str(f).split('.')[1]
> hidden[fname] = r[fna
On Tuesday, November 29, 2016 at 11:00:06 AM UTC-5, Annet wrote:
>
> I wonder whether there is a validator on auth_membership user_id and
> group_id
>
> I found that I can add the same membership multiple times which is not
> what I want.
>
There are no validators that prevent duplicates, but if
You are missing a bunch of files
(index):19 GET https://spinjazz.net/new_spin2/static/js/jquery.js
(index):19 GET https://spinjazz.net/new_spin2/static/css/calendar.css
(index):19 GET https://spinjazz.net/new_spin2/static/js/calendar.js
(index):19 GET https://spinjazz.net/new_spin2/static/js/we
Thanks Leonel
I am not missing the http equivalents, so where is routing different for
https to http in web2py?
Peter
On Tuesday, 29 November 2016 17:05:35 UTC, Leonel Câmara wrote:
>
> You are missing a bunch of files
>
> (index):19 GET https://spinjazz.net/new_spin2/static/js/jquery.js
> (i
In my routes.py I have
routes_in = ((r'.*://spinjazz.net:\w* /static/$anything',
r'/new_spin2/static/$anything'),
presumably this is routing only http correctly can anyone tell me how I can
get it to work for https
Thanks
Peter
--
Resources:
- http://web2py.com
- http://web2py.com/book (Docu
Running with python 3 or python 2 the code will support both version as
long as your app comply py3...
On Thu, Nov 24, 2016 at 6:25 AM, Marlysson Silva
wrote:
> Support to py3 you say running with python3 web2py.py ? Or just
> internally ?
>
>
> Em sábado, 19 de novembro de 2016 17:15:00 UT
Or you can create a constrains at backend level specifying that both fields
as to be unique.
The drawback is that you will get web2py ticket in case the insert fails...
Something like :
CREATE TABLE example (
a integer,
b integer,
c integer,
*UNIQUE (a, c)*
);
ALTER TABLE tablen
Thanks, Anthony.
1. I thought f.name gives the name as . but for the hidden
fields and form1.element, the field name alone is required. I will make a
note of it.
2. hidden is included to make sure that the update back end operation does
not make those fields as NULL. Not sure if the below alte
17 matches
Mail list logo