Consider it done.
On Thursday, February 20, 2020 at 8:02:45 PM UTC-8, Massimo Di Pierro wrote:
>
> No obvious solution yet but will prioritize this. Would you mind opening
> an issue on github about this?
>
> On Wednesday, 19 February 2020 12:33:32 UTC-8, Carlos Hanson wrote:
>>
>> It looks like
No obvious solution yet but will prioritize this. Would you mind opening an
issue on github about this?
On Wednesday, 19 February 2020 12:33:32 UTC-8, Carlos Hanson wrote:
>
> It looks like table inheritance is affected by the same issue:
>
>
> monster = db.Table(db, 'monster', Field('color'), Fi
It looks like table inheritance is affected by the same issue:
monster = db.Table(db, 'monster', Field('color'), Field('size'))
db.define_table('thing', Field('name'), monster)
The following traceback is the same as the error using
_enable_record_versioning() starting at *table = self.lazy_def
Greetings,
I just started using py4web, and I'm very excited to do so.
Has there been any more thought on this issue? I was partially into a new
web2py app in which I use _enable_record_versioning(), and I am migrating
it to py4web.
Thanks.
On Saturday, August 17, 2019 at 10:34:21 PM UTC-7,
Sorry for the late response. I just run into this myself. Do not have a
good solution at this time, unless we make pydal aware of
ThreadSafeVariable(s). Maybe we have to.
On Wednesday, 31 July 2019 05:05:50 UTC-7, Manuel Vio wrote:
>
> Ok, I narrowed the problem a bit:
>
> In py4web/core.py, aro
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, _, threadsaf
6 matches
Mail list logo
