I tried to use migrate_enabled but i having returned the following
error:
p4089
sS'key'
p4090
S"'migrate_enabled'"
p4091
sssS'traceback'
p4092
S'Traceback (most recent call last):\n File "/home/dotcloud/current/
gluon/restricted.py", line 181, in restricted\n exec ccode in
environment\n File "/home/dotcloud/1303836474.97/applications/wiki/
models/plugin_wiki.py", line 63, in <module>\n format = \'%(slug)s
\', migrate_enabled=plugin_wiki_migrate)\n File "/home/dotcloud/
current/gluon/dal.py", line 3992, in define_table\n raise
SyntaxError, \'invalid table "%s" attribute: %s\' % (tablename, key)
\nSyntaxError: invalid table "plugin_wiki_page" attribute:
migrate_enabled\n'
p4093
Oscar.
On 26 abr, 08:23, Massimo Di Pierro <massimo.dipie...@gmail.com>
wrote:
> Than the safe way is:
>
> 1) delete database
> 2) recreate database (empty, no tables)
> 3 use
>
> DAL('mysql://...') # the default with no arguments like
> migrate_enabled=True, fake_migrate_enabled=True
>
> On Apr 26, 1:03 am, Oscar <oscar.m...@gmail.com> wrote:
>
>
>
>
>
>
>
> > Thank you for your reply,
>
> > On 25 abr, 18:09, Massimo Di Pierro <massimo.dipie...@gmail.com>
> > wrote:
>
> > > On a new database you should run at least once with migrate=True and
> > > then you can set migrate=False and it should work.
>
> > I did it, and didn't work.
>
> > > If you are getting the errors below I assume you have migrate=True and
> > > missing database/*.table files. You must have deleted them.
>
> > Nope, it's error just happens when I change from SQLite to Postgre,
> > using SQlite all works fine, then I change to Postgre it works without
> > issue while migrate = True, if I switch it to False Application
> > complaint with described error.
>
> > > 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.
>
> > I don't care to recover any data, I just want that it work without
> > issue.
>
> > > 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.
>
> > Regards,
>
> > Oscar.
