You are in a mess because your sqlite table does not reflect your
define_table for 'repo'.
If you include auth.signature, then you should also have these fields:
Field('is_active', 'boolean', default=True),
Field('created_on', 'datetime', default=request.now),
Field('created_by', db.auth_user, default=auth.user_id),
Field('modified_on', 'datetime', update=request.now),
Field('modified_by', db.auth_user, update=auth.user_id)
You also have a 'status' field. BTW 'status' is a reserved word on many
DBs, so it is best avoided. In any case, this field name has no special
meaning in Web2py.
*So, what to do?* I suggest...
- Do not use web2py for transferring the data.
- Download some Sqlite manager software from the web
<https://www2.sqlite.org/cvstrac/wiki?p=ManagementTools>,
- Using that software
- open up your ./databases/storage.sqlite file and see exactly what
fields you've got.
- export the data.
- You should then be able to import that file into MariaDB.
- To use the new MariaDB table, correct your web2py table definition to
reflect the actual fields.
- Do a fake_migrate in web2py. fake_migrate=True, migrate=True
- Check the table definition file exists in yourapp/databases folder
Good luck!
--
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/3121661d-416a-4aee-9dc0-d2b8b16771aa%40googlegroups.com.
