round does the
trick, but maybe a better approach would be using a custom field to store
user's status.
Cheers
Manuel Vio
Il giorno giovedì 12 gennaio 2017 15:23:28 UTC+1, Andrea Fae' ha scritto:
>
> Hello,
> I want to use both local and domain AD authentication.
> I did the job but
+1
Il giorno domenica 23 aprile 2017 05:35:29 UTC+2, lucas ha scritto:
>
> hey everyone,
>
> I think we should recognize and congratulate Massimo and the developers of
> web2py. its been nearly a year since the last production update and the
> whole platform is just excellent.
>
> it is the
Hi, I think I had the same problem, in my case it was a DAL constructor
parameter changing its value in new web2py versions. Try to revert
entity_quoting parameter to False as per this issue ticket I filed:
https://github.com/web2py/web2py/issues/1697
See also
here:
Hi, recently I had an SQL issue upgrading web2py too. A DAL constructor
default parameter (entity_quoting) changed his value and my application
crashed.
Maybe your case differs, but you can try reverting entity_quoting to False
and see if this works.
You can get more info here:
Ok, I narrowed the problem a bit:
In py4web/core.py, around line 207, there is this adjustment in order to
make some variables threadsafe:
# make sure some variables in pydal are thread safe
for _ in ['readable', 'writable', 'default', 'update', 'requires']:
setattr(pydal.DAL.Field, _,
Hi, I'm testing py4web and I'm stuck with record versioning.
If in models.py I define a trivial table with versioning enabled like this:
### Define you table below
#
# db.define_table('thing', Field('name'))
#
## always commit your models to avoid problems later
#
# db.commit()
#
6 matches
Mail list logo
