MySql signed primary key migration about mikro-orm HOT 3 CLOSED

@PrimaryKey({ autoincrement: false, type: new BigIntType('bigint'), unsigned: false })`
id!: number;

Just FYI this definition does not make much sense, you use new BigIntType('bigint'), but map to a JS number? Sounds like you want this instead:

@PrimaryKey({ autoincrement: false, unsigned: false })`
id!: bigint;

(it won't fix the problem you are reporting, but at least you won't be lying to yourself - the ORM would hydrate bigints there, not numbers.

from mikro-orm.

Just FYI this definition does not make much sense, you use new BigIntType('bigint'), but map to a JS number?

Yes I believe I originally did that since I do want a JS number, but MySQL int does not support same max/min value as JS number so I was getting errors saving some values to the database.

from mikro-orm.

Yes I believe I originally did that since I do want a JS number, but MySQL int does not support same max/min value as JS number so I was getting errors saving some values to the database.

My point is that new BigIntType('bigint') means "bigint column that maps to bigint JS type". If you want to map to JS number, you need new BigIntType('number'), if you want to map to JS bigint, you should declare the property type as bigint (and in such case, you don't need to explicitly use the BigIntType as mentioned in the previous comment).

from mikro-orm.