typeorm decimal value of column repeatedly generating migration ?

[dhiraj-ppp]

Issue type:

[ ] question
[x] bug report
[ ] feature request
[ ] documentation issue

Database system/driver:

[ ] cordova
[ ] mongodb
[ ] mssql
[x] mysql / mariadb
[ ] oracle
[ ] postgres
[ ] cockroachdb
[ ] sqlite
[ ] sqljs
[ ] react-native
[ ] expo

TypeORM version:

[x] latest
[ ] @next
[ ] 0.x.x (or put your version here)

Steps to reproduce or a small repository showing the problem:

import {Entity, PrimaryGeneratedColumn, Column} from "typeorm";

@Entity()
export class User {

    @PrimaryGeneratedColumn()
    id: number;

    @Column()
    firstName: string;

    @Column()
    lastName: string;

    @Column()
    age: number;

    @Column()
    city: number;

    @Column({ type: 'decimal', precision: 22, scale: 2,default: 0.00 })
    bday: number;

}

Migration

import {MigrationInterface, QueryRunner} from "typeorm";

export class Adddecl1590562535409 implements MigrationInterface {
    name = 'Adddecl1590562535409'

    public async up(queryRunner: QueryRunner): Promise<void> {
        await queryRunner.query("ALTER TABLE `user` CHANGE `bday` `bday` decimal(22,2) NOT NULL DEFAULT 0");
    }

    public async down(queryRunner: QueryRunner): Promise<void> {
        await queryRunner.query("ALTER TABLE `user` CHANGE `bday` `bday` decimal(22,2) NOT NULL DEFAULT '0.00'");
    }

}

I continually getting migrations generated even after running them. I am not making any changes in Schema.
Step:1 Generate a migration
Step :2 Run a migration
Step :3 Generate a migration

As per step 3 migration should not be generated because i have already ran the migration and made no changes in DB scheme since i ran migration.

Note:
If i don't set the default value in schema then i don't get any migration generated on step 3.

[maratumba]

This exact issue is seen on Postgres today on typeORM 0.3.20

[AdilSarwarNU]

can confirm this happening in a project of ours. using 'decimal' type - Any fixes on this?

[codewithalihamza]

Anyone Please tell me about the solution to this bug?