This is a brand new project since the consensus was I could not continue with the previous project since I removed all of the migration files.
Two separate, but most likely related, bugs. Correct, the change(s) appear to work, but do not generate a file.
- The first issue in creating a brand new project and tables happened in Database Manager bugs - #3 by kfawcett. this is where after adding a multi-reference field, Wappler database manager corrupted something. I’m guessing it has something to do with how it creates a separate table via the multi-reference field. I didn’t notice an issue until I went to create the next field, which was the isActive field on user table. This threw an error about roleid related to the previous change. So I tried one more time resulting in two change files with the same name.
I ended up removing one of the change files and modifying the second change migration file to only contain the isActive field addition and then I was able to apply the change successfully.
Here’s the code that should only include the isActive field, but somehow has duplicated the changes from the previous change I performed.
My guess to the cause? Either something in the code that generates the multi-reference table or one of the schema refreshes I attempted caused this issue.
Here’s the original code that should only contain the isActive field addition to the user table.
exports.up = function(knex) {
return knex.schema
.createTable('Roleusers', async function (table) {
table.uuid('RoleId');
table.foreign('RoleId').references('id').inTable('role').onUpdate('CASCADE').onDelete('CASCADE');
table.uuid('UserId');
table.foreign('UserId').references('id').inTable('user').onUpdate('CASCADE').onDelete('CASCADE');
})
.table('user', async function (table) {
table.boolean('isActive');
})
};
exports.down = function(knex) {
return knex.schema
.table('user', async function (table) {
table.dropColumn('isActive');
})
.dropTable('Roleusers')
.dropTable('Rolepermissions')
};
Here’s the modified code:
exports.up = function (knex) {
return knex.schema
.table('user', async function (table) {
table.boolean('isActive');
})
};
exports.down = function (knex) {
return knex.schema
.table('user', async function (table) {
table.dropColumn('isActive');
})
};
If you’re thinking “well he must have lumped those two changes together”. The answer is no, because here is the migration file that I created directly before attempting to add the isActive to the user table. You can see that it has two createTable actions for the Rolepermissions and Roleusers tables. So why, are they appearing again in the next migration file?
exports.up = function(knex) {
return knex.schema
.table('role', async function (table) {
table.string('name');
table.uuid('createdBy');
table.foreign('createdBy').references('id').inTable('user').onUpdate('CASCADE').onDelete('CASCADE');
table.uuid('updatedBy');
table.foreign('updatedBy').references('id').inTable('user').onUpdate('CASCADE').onDelete('CASCADE');
table.datetime('createdDate').defaultTo(knex.fn.now());
table.datetime('updatedDate').defaultTo(knex.fn.now());
table.string('shortDescription');
table.text('description');
table.boolean('isActive');
})
.createTable('Rolepermissions', async function (table) {
table.uuid('RoleId');
table.foreign('RoleId').references('id').inTable('role').onUpdate('CASCADE').onDelete('CASCADE');
table.uuid('PermissionId');
table.foreign('PermissionId').references('id').inTable('permission').onUpdate('CASCADE').onDelete('CASCADE');
})
.createTable('Roleusers', async function (table) {
table.uuid('RoleId');
table.foreign('RoleId').references('id').inTable('role').onUpdate('CASCADE').onDelete('CASCADE');
table.uuid('UserId');
table.foreign('UserId').references('id').inTable('user').onUpdate('CASCADE').onDelete('CASCADE');
})
};
exports.down = function(knex) {
return knex.schema
.dropTable('Roleusers')
.dropTable('Rolepermissions')
.table('role', async function (table) {
table.dropColumn('name');
table.dropForeign('createdBy');
table.dropColumn('createdBy');
table.dropForeign('updatedBy');
table.dropColumn('updatedBy');
table.dropColumn('createdDate');
table.dropColumn('updatedDate');
table.dropColumn('shortDescription');
table.dropColumn('description');
table.dropColumn('isActive');
})
};
- So, I’m past the previous error. But now, when I try to make any new changes no migration files are created, but the changes do get applied in the db.json file. I’m guessing the error
Cannot read properties of undefined (reading 'name') has something to do with it.
