| .. |
|
20170925191833-create-bans-table.js
|
871235f81b
The names of the migration file table references must match the casing specified by the models when they get created. Hence the issue where tables cannot be found when running npm run start.
|
5 years ago |
|
20170925200317-create-categories-table.js
|
871235f81b
The names of the migration file table references must match the casing specified by the models when they get created. Hence the issue where tables cannot be found when running npm run start.
|
5 years ago |
|
20170925201609-create-ips-table.js
|
871235f81b
The names of the migration file table references must match the casing specified by the models when they get created. Hence the issue where tables cannot be found when running npm run start.
|
5 years ago |
|
20170925201924-create-logs-table.js
|
871235f81b
The names of the migration file table references must match the casing specified by the models when they get created. Hence the issue where tables cannot be found when running npm run start.
|
5 years ago |
|
20170925202317-create-notifications-table.js
|
871235f81b
The names of the migration file table references must match the casing specified by the models when they get created. Hence the issue where tables cannot be found when running npm run start.
|
5 years ago |
|
20170925202519-create-pollanswers-table.js
|
871235f81b
The names of the migration file table references must match the casing specified by the models when they get created. Hence the issue where tables cannot be found when running npm run start.
|
5 years ago |
|
20170925202651-create-pollquestions-table.js
|
871235f81b
The names of the migration file table references must match the casing specified by the models when they get created. Hence the issue where tables cannot be found when running npm run start.
|
5 years ago |
|
20170925202801-create-pollvotes-table.js
|
871235f81b
The names of the migration file table references must match the casing specified by the models when they get created. Hence the issue where tables cannot be found when running npm run start.
|
5 years ago |
|
20170925203055-create-postnotifications-table.js
|
871235f81b
The names of the migration file table references must match the casing specified by the models when they get created. Hence the issue where tables cannot be found when running npm run start.
|
5 years ago |
|
20170925203433-create-posts-table.js
|
871235f81b
The names of the migration file table references must match the casing specified by the models when they get created. Hence the issue where tables cannot be found when running npm run start.
|
5 years ago |
|
20170925204011-create-reports-table.js
|
871235f81b
The names of the migration file table references must match the casing specified by the models when they get created. Hence the issue where tables cannot be found when running npm run start.
|
5 years ago |
|
20170925204327-create-settings-table.js
|
871235f81b
The names of the migration file table references must match the casing specified by the models when they get created. Hence the issue where tables cannot be found when running npm run start.
|
5 years ago |
|
20170925204827-create-threads-table.js
|
871235f81b
The names of the migration file table references must match the casing specified by the models when they get created. Hence the issue where tables cannot be found when running npm run start.
|
5 years ago |
|
20170925205531-create-user_post-table.js
|
ab68e83f94
Use utf8mb4 encoding
|
8 years ago |
|
20170925205649-create-userip-table.js
|
871235f81b
The names of the migration file table references must match the casing specified by the models when they get created. Hence the issue where tables cannot be found when running npm run start.
|
5 years ago |
|
20170925205832-create-users-table.js
|
871235f81b
The names of the migration file table references must match the casing specified by the models when they get created. Hence the issue where tables cannot be found when running npm run start.
|
5 years ago |
|
20170925210453-create-admintokens-table.js
|
871235f81b
The names of the migration file table references must match the casing specified by the models when they get created. Hence the issue where tables cannot be found when running npm run start.
|
5 years ago |
|
20170927123720-add-show-description-column.js
|
871235f81b
The names of the migration file table references must match the casing specified by the models when they get created. Hence the issue where tables cannot be found when running npm run start.
|
5 years ago |
|
20171203220305-add-picture-column.js
|
871235f81b
The names of the migration file table references must match the casing specified by the models when they get created. Hence the issue where tables cannot be found when running npm run start.
|
5 years ago |
|
20171208231827-create-profile-picture-table.js
|
871235f81b
The names of the migration file table references must match the casing specified by the models when they get created. Hence the issue where tables cannot be found when running npm run start.
|
5 years ago |
|
20171208235706-add-profile-picture-column.js
|
871235f81b
The names of the migration file table references must match the casing specified by the models when they get created. Hence the issue where tables cannot be found when running npm run start.
|
5 years ago |
|
20180104141055-create-session-table.js
|
871235f81b
The names of the migration file table references must match the casing specified by the models when they get created. Hence the issue where tables cannot be found when running npm run start.
|
5 years ago |
|
20181209110718-add-plaintext-column.js
|
871235f81b
The names of the migration file table references must match the casing specified by the models when they get created. Hence the issue where tables cannot be found when running npm run start.
|
5 years ago |
nher1625