#692 Prosody migrator creates incorrect db schema when moving data from file storage to sqlite
Steps to reproduce:
1. Install prosody with default settings (internal file-based storage)
2. Add a user (user1@domain), set a password, and add one contact
3. Configure migrator to migrate from file-based storage to sqlite3
4. Run migrator
5. Configure prosody to use the newly-created sqlite3 database
6. Attempt to change user's password with prosodyctl
7. Add a new user (user2@domain) with prosodyctl, set a password, and add one contact
8. Observe sqlite3 database and compare data format between user1 and user2
1. Prosody migrator's schema for migrating existing users matches the schema used by prosodyctl when adding new users
2. Prosody migrator's schema for migrating other data (roster, vcard, etc) matches the schema used by prosody when creating this data initially using the sqlite3 database backend
1. Using the migrator to move from internal storage to sqlite3 creates a database with an incorrect schema
2. Due to the incorrect schema, prosodyctl cannot detect that there are existing users
3. Due to the incorrect schema, Prosody will not allow migrated users to log in
Ubuntu 14.04.3 LTS
Prosody 0.10 nightly build 264 (2016-06-12, 82d8c11ab0cb)
The migrator does not populate the "host" field and mixes up the "user" and "store" fields, resulting in a mangled database.
Here's a screenshot of a database created by the migration tool from existing user data (user1) and with another user added afterward (user2) by prosodyctl
I can't seem to reproduce this. Can you describe more about your setup? Version of LuaDBI?
Closing for inactivity and inability to reproduce.