Hi Dave, Finally i got to the root of the problem :-) Turns out to be a.... builders error ... yes, my own error.
In the very first table there is a reference to a logged in user which does not exist when trying to create the tables ( same for loading the data). Quick work around is swapping two tables and after that prefill the first table with a couple of records. After that i could upload my backup data withoout a problem. Thanks for the help. Rgards, Steve Op donderdag 12 september 2019 10:49:15 UTC+2 schreef Dave S: > > > > On Wednesday, September 11, 2019 at 1:55:04 PM UTC-7, Steve wrote: >> >> Hi Dave, >> >> After performing a Fake_migration_all=True the Db files where created in >> de app/databases folder. >> So, in de admin i can see all of the tables..... >> >> But, unfortunatly the tables where NOT created in the MySQL database. >> I can't find ou why not or how to fix this. >> >> > fake_migration ONLY creates *.table files, and is primarily for already > existing tables (e.g., legacy) DBs. To create an actual DB table requires > migration rather than fake_migration. And as Niphlod has often pointed > out, migrate=True only needs to be set for one access, and then you turn it > back off. > > /dps > > -- 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 message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/web2py/da151e9d-573d-4274-a07b-b1341b9d8ead%40googlegroups.com.
