The documentation states the SQLite lacks a boolean data type, so PyDAL
maps boolean values to CHAR(1). But why do you do this with Postgres?
Looking in my migration logs, I see boolean fields being created as
CHAR(1). Postgres does have a boolean type.
John
--
Resources:
- http://web2py.c
I think all this bears some brainstorming in light of what’s going on with
Webassembly.
I’m not saying Javascript for building web UIs isn’t the future, but...
Ok, quick show of hands: How many people absolutely adore Javascript? Oh wait,
it doesn’t matter, because we have no choice. Or do we
. This architecture is a very good idea, and
will teach marketable skills (Python and JavaScript/Vue.js), but I wish young
students had more choices for front-end languages. Hopefully Webassembly is
starting to change that.
John Underhill
QIS Project, Inc.
Santa Barbara, California
From
@João, you are programming yourself into a corner. No matter what you do,
you’ll keep running into more problems. The reason for this is because you’re
trying to do atomic operations at the application level. You simply can’t do
that.
If you check whether or not something is locked at the ap
4 matches
Mail list logo