On Tuesday, June 6, 2017 at 2:36:19 AM UTC-4, Doug Taylor wrote:
>
> This is becoming a show-stopper for me now as I cannot ADD fields to an
> exiting table either.
>
It shouldn't be a show stopper, as you can always migrate the database via
other means. Just use an external tool, or simply run
Just some thought not solution... Maybe you could try to decouple your data
from your table, by doing so you then will be able to flush the entire
model instead of just modify it (ALTER), that way you will avoid the issue
with rname.
You can use this trick to decouple your basic required data :
This is becoming a show-stopper for me now as I cannot ADD fields to an
exiting table either. I'm pretty sure adding fields worked before when I
was running on Windows. Made the transition to Linux on my office desktop
recently and that was when I first encountered the problem. Adding the
field
Thanks Doug,
I was understanding that, it much clearer now though. Your use case for
rname seems exactly what rname is for.
Good luck
Richard
On Wed, May 31, 2017 at 6:15 PM, Doug Taylor wrote:
> Hi Richard -
>
> Thanks for response. I am running web2py version:
> Version 2.14.6-stable+timest
Hi Richard -
Thanks for response. I am running web2py version:
Version 2.14.6-stable+timestamp.2016.05.10.00.21.47
I'm using rname because postgresql doesn't like case sensitive table and
field names much, and neither do my colleagues, but I like CamelCase in my
code, so as you say, for code re
Hi Doug,
I am not sure I follow and understand the exact problem, it maybe me, but
can you provide model before and after and.
You may also try to reproduce the bug and explain the exact step to trigger
it and pack an dummy app to facilitate the reproducing of the bug for us.
Also, specify the v
6 matches
Mail list logo
