from 0 to 255 before MySQL 5.0.3, and 0 to
> 65,535 in 5.0.3 and later versions".
>
> We set varchar max to 255 to avoid problems with older versions of
> mysql. Since problems were reported by users.
> There should not have been a migration in your case. I will look in
&g
lengths.
On Jan 22, 11:48 am, "Jonathan Z." wrote:
> Massimo,
>
> Here is an example of one of the tables that got a truncated field:
>
> before...
>
> db.define_table("thing",
> Field("user_id", db.auth_user, notnull=True, readable=False
ritable=False),
format="%(title)s"
)
After this change (addition of a new field) and subsequent DB
migration, the "description" field was truncated from 2048 characters
to 255. Note that this change didn't alter the field length on
sqlite. But it did truncate the d
I have a number of fields specifying a length > 255 (some as large as
2K). On a recent schema migrate, web2py truncated all of these fields
to 255, resulting in substantial data loss.
My database is mysql. I'm on version 1.91.6 of web2py. I'm pretty
sure this has something to do with the new DA
Has anyone tried integrating celery with web2py? If not, is there a
recommended task queue (beyond the lightweight option mentioned in the
"Core" chapter of the web2py book)?
I'm kicking off a threaded process. As part of the "run" method, I'm
calling: env("application", import_models=True) in order to work with
the web2py environment inside the context of my thread. As a result,
models are parsed and the following exception is raised:
Traceback (most recent call las
6 matches
Mail list logo
