On Tuesday, 11 September 2012 21:43:10 UTC-5, Matt wrote:
>
> Hi Massimo,
>
> I've switched to trunk and yes the fields are now being created as
> expected.
>
> As a suggestion could the auto migration have an extra check added to
> ensure that "upload" columns - if on non filesystem environmen
Hi Massimo,
I've switched to trunk and yes the fields are now being created as expected.
As a suggestion could the auto migration have an extra check added to
ensure that "upload" columns - if on non filesystem environments like GAE -
alway create the equivalent _blob column?
Thankfully even t
I found the web2py bug that caused this problem. It was an indentation
issue. Took the occasion to rewrite the logic a little better.
Can you please check this works now? You should be able to update to trunk
and your missing fields should re-appear (they will be hidden,
writable=False, readabl
Let me add you did not lose your data. If you revert to 1.99.7 you should
find the data is still there.
Yet we need to understand what is happening
On Tuesday, 11 September 2012 03:44:46 UTC-5, Matt wrote:
>
> Hi there,
>
> First off thanks for all of the fantastic work putting 2.0 together.
Please open a ticket about this. You say the problem is on GAE but the
ticket refers to MySQLdb. I assume these are two different systems.
On Tuesday, 11 September 2012 03:44:46 UTC-5, Matt wrote:
>
> Hi there,
>
> First off thanks for all of the fantastic work putting 2.0 together.
> Looking fo
5 matches
Mail list logo
