Database Manager - Big Increment references still being created as integer type instead of BigInt

[that_cheeseguy]

Wappler Version : 4.8.2
Operating System : MacOS Monterey - M1
Server Model: NodeJS
Database Type: Postgres
Hosting Type: Own Server

Expected behavior

As of the 4.8.3 update, reference fields should now always use the destination field type as reference data type.

Actual behavior

What actually happens?

However, it looks like bigIncrements are still being set as regular integer references. I made a subtable just to test, and the app_user_id should be a bigInt but it looks like it is still being set as an integer. This is the content of the migration file:

exports.up = function(knex) {
  return knex.schema
    .createTable('app_user_temp_table', async function (table) {
      table.increments('id');
      table.integer('app_user_id').unsigned();
      table.foreign('app_user_id').references('id').inTable('app_user').onUpdate('CASCADE').onDelete('CASCADE');
    })
};

exports.down = function(knex) {
  return knex.schema
    .dropTable('app_user_temp_table')
};

The table.integer('app_user_id').unsigned(); should be table.bigInteger('app_user_id').unsigned();

I’ve tried with experimental features on and off.

[Teodor]

This has been fixed in Wappler 4.9.0