[web2py] Re: Yet Another Migration Problem

2018-10-17 Thread Dave S
Never mind, it's the old problem of using Field("distance", 'decimal(5, 1)', default=None, writable=False), instead of Field("distance", 'decimal(5,1)', default=None, writable=False), The application is now working (as is appadmin) ... but I don't see any table files. /dps -- R

[web2py] Re: Yet Another Migration Problem

2018-10-17 Thread Dave S
It's happening to me again: On Wednesday, February 7, 2018 at 1:00:19 AM UTC-8, Dave S wrote: > > Copying an app from 2.14.6 to 2.16.1, including copying the database file > (storage.sqlite because, well, I'm using sqlite on this machine). > > appconfig.ini has migrations off, and db.py has > >

[web2py] Re: Yet Another Migration Problem

2018-02-08 Thread Leonel Câmara
You're probably using migrate_enabled=False in your config in production since you're copying the database file from the dev version. -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issu

[web2py] Re: Yet Another Migration Problem

2018-02-08 Thread Dave S
On Thursday, February 8, 2018 at 6:48:12 AM UTC-8, Leonel Câmara wrote: > > This isn't a migration problem at all. You are creating the rows object > wrongly you need to change this line: > > rowed = Rows(db) > > to > > rowed = Rows(db, fields=rows.fields, colnames=rows.colnames); > > I can beli

[web2py] Re: Yet Another Migration Problem

2018-02-08 Thread Leonel Câmara
This isn't a migration problem at all. You are creating the rows object wrongly you need to change this line: rowed = Rows(db) to rowed = Rows(db, fields=rows.fields, colnames=rows.colnames); BTW this is some weird code for me, very hard to understand. I don't understand why you need rowed at

[web2py] Re: Yet Another Migration Problem

2018-02-07 Thread Dave S
On Wednesday, February 7, 2018 at 12:02:41 PM UTC-8, Dave S wrote: > > I did not try renaming the copied table files to have no hash. > > Now I have, and it doesn't seem to have made a difference. /dps -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github

[web2py] Re: Yet Another Migration Problem

2018-02-07 Thread Dave S
On Wednesday, February 7, 2018 at 11:09:09 PM UTC-8, Dave S wrote: > > > > On Wednesday, February 7, 2018 at 2:08:23 PM UTC-8, Leonel Câmara wrote: >> >> Hummm you're right, can I see the code for default/sorted and the >> quartermaster table? >> > > > db.define_table('QuarterMaster', >

[web2py] Re: Yet Another Migration Problem

2018-02-07 Thread Dave S
On Wednesday, February 7, 2018 at 2:08:23 PM UTC-8, Leonel Câmara wrote: > > Hummm you're right, can I see the code for default/sorted and the > quartermaster table? > db.define_table('QuarterMaster', Field('IssueYr', 'integer', requires = [IS_NOT_EMPTY(),

[web2py] Re: Yet Another Migration Problem

2018-02-07 Thread Leonel Câmara
Hummm you're right, can I see the code for default/sorted and the quartermaster table? -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this

[web2py] Re: Yet Another Migration Problem

2018-02-07 Thread Dave S
On Wednesday, February 7, 2018 at 4:05:17 AM UTC-8, Leonel Câmara wrote: > > You are using fake migrate. It thinks it has migrated but it hasn't and > the column isn't on the DB. Remove the field in the table and do another > fake migration. Then put the field back and do a real migration. > A

[web2py] Re: Yet Another Migration Problem

2018-02-07 Thread Leonel Câmara
You are using fake migrate. It thinks it has migrated but it hasn't and the column isn't on the DB. Remove the field in the table and do another fake migration. Then put the field back and do a real migration. -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://g