On Saturday, April 7, 2018 at 4:13:16 AM UTC-4, Stephan wrote:
>
> Anthony, 1kTHX, it works now.
> The error was, that I set *migrate=True* in the DAL connector, i.e. *db
> = DAL('credentials.ee@mysql', migrate=True)* but not in the table that
> was altered.
> So this works for me:
> - I run th
On Thursday, April 5, 2018 at 5:39:38 PM UTC-4, Stephan wrote:
>
> I got the error afterwards, i.e. I ran fake_migration_all (without errors)
> and then I altered a table and kicked migrate=true. That's where I ran into
> the same error as before.
>
*.table files are in the /databases folder. Th
I got the error afterwards, i.e. I ran fake_migration_all (without errors)
and then I altered a table and kicked migrate=true. That's where I ran into
the same error as before.
Am Donnerstag, 5. April 2018 22:54:16 UTC+2 schrieb Anthony:
>
> Need to see your code. With fake_migrate_all=True, the
Need to see your code. With fake_migrate_all=True, the DAL will generate
migration files but no run any migrations, so you cannot get that error.
Anthony
On Thursday, April 5, 2018 at 11:49:38 AM UTC-4, Stephan wrote:
>
> Hi Antony,
> does not seem to work.
> I still get an error by setting mig
Hi Antony,
does not seem to work.
I still get an error by setting migrate to true. In which directory are the
*.table file written to?
thx
(1050, "Table 'auth_user'
already exists")Version
web2py™ Version 2.8.2-stable+timestamp.2013.11.28.13.54.07Traceback
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11
Probably you don't have *.table files indicating the current status of the
database schema. First, without the new column in the code, run a request
with fake_migrate_all=True, which will create an updated set of *.table
files. Then add the new column, and the migration should work.
Anthony
On
6 matches
Mail list logo
