Re: [web2py] Re: Changing main repo and database model modifications

Sorry Clemens, I hadn't checked your link correctly, it states it clearly with pseudo code how the flags work. Thanks, Jon. if DAL.migrate_enabled and table.migrate: if DAL.fake_migrate_all or table.fake_migrate: perform fake migration else: perform migration

Re: [web2py] Re: Changing main repo and database model modifications

Thanks Jim. Libre de virus. www.avast.com <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Tue, Dec 8,

Re: [web2py] Re: Changing main repo and database model modifications

I believe it will then perform the migration, but instead of running the migrations on the database, it will just update the files in /databases. -Jim On Tuesday, December 8, 2020 at 2:07:12 AM UTC-6 Jonsubs wrote: > Hi Jim, > Just one question, what happens when you set migrate=True and >

Re: [web2py] Re: Changing main repo and database model modifications

Hi Clemens, Just some quick questions. 1) What happens with auth tables and python -S -M -P? it does not seem to create the .table files 2) Regarding migration and fake migration. I tried to summarize my understanding in the table below (use a fixed width font to see it properly). How does

Re: [web2py] Re: Changing main repo and database model modifications

Hello Jon, yes, this should do it. It's also fine to import an export of an existing DB. But you can just start your application, this should create the .table files at the first, I think. Regards Clemens P.S.: Concerning migrate and fake_migrate options have a look there:

Re: [web2py] Re: Changing main repo and database model modifications

Hi Jim, Just one question, what happens when you set migrate=True and fake_migrate=True at the same time? Thanks, Jon. On Mon, Dec 7, 2020 at 8:47 PM Jim S wrote: > Can you try setting migrate=True, fake_migrate=True and > fake_migrate_all=True in the new repo? > > either that, or copy the

Re: [web2py] Re: Changing main repo and database model modifications

Thanks Clemens and Jim S. So I guess that I should use the "python web2py.py -M -S " command option to create the new table files, right? On Mon, Dec 7, 2020 at 8:54 PM Clemens wrote: > Please try *not* to use the .table files. You can just rename database > folder to database.orig and create

[web2py] Re: Changing main repo and database model modifications

Please try *not* to use the .table files. You can just rename database folder to database.orig and create a new database folder in your application directory. This is necessary since on the "new machine" there are new databases created, I guess. Have a try. If it's solve the problem you can

[web2py] Re: Changing main repo and database model modifications

Can you try setting migrate=True, fake_migrate=True and fake_migrate_all=True in the new repo? either that, or copy the databases directory over from old repo to the new repo. -Jim On Monday, December 7, 2020 at 9:10:06 AM UTC-6 Jonsubs wrote: > Oh, I forgot to comment (and I believe it may

[web2py] Re: Changing main repo and database model modifications

Oh, I forgot to comment (and I believe it may be relevant) that I'm using a MySQL database. And when I try to add a new column to a previously defined table (defined and created originally in another repo) I do get the error below: InternalError: (1054, u"Unknown column 'tag.in_between' in