On a new database you should run at least once with migrate=True and then you can set migrate=False and it should work.
If you are getting the errors below I assume you have migrate=True and missing database/*.table files. You must have deleted them. In this case you must run with DAL(....,migrate_enabled=True, fake_migrate_enabled=True) and it will rebuild the missing .table files. Mind the process is not guaranteed to recover the missing files. On Apr 25, 3:39 pm, Oscar <oscar.m...@gmail.com> wrote: > Sorry again, > > The error is: ProgrammingError: relation "auth_user" already exists > > Oscar. > > On 25 abr, 16:34, Oscar <oscar.m...@gmail.com> wrote: > > > > > > > > > BTW I tried with migration set to False locally with SqLite and it > > worked without issues. > > > Oscar. > > > On 25 abr, 16:32, Oscar <oscar.m...@gmail.com> wrote: > > > > Hi there, > > > > I'm triying to deploy a W2P project based on Wiki_Plugin. I just > > > installed the plugin, I did some tests using sqlite, then I wanted to > > > deploy the code over my server based on PostgreSQL, I did the same and > > > it worked with migrations set to True, but wiki plugins has a comment > > > where I must set to False the migration in a production environment, I > > > did set it but the application fails. The error is related with > > > auth_user table already exists, so If migrations are turned off, is > > > the default behaviour of w2p consider all tables as these already > > > exists? > > > > How I can fix this? > > > > Regards, > > > > Oscar.
