In my NestJs project using TypeORM, I have the following column definition in an entity:
@CreateDateColumn({
nullable: true,
type: 'timestamp',
default: () => 'NULL',
})
public succeededAt?: Date;
A migration is generated with the correct structure:
export class migration123 implements MigrationInterface {
name = 'migration123';
public async up(queryRunner: QueryRunner): Promise\<void\> {
await queryRunner.query(
`CREATE TABLE [...], "succeededAt" TIMESTAMP DEFAULT NULL, [...]`
);
\[...\]
}
However, when I try to generate a new migration with TypeORM CLI after running this migration, it still detects differences:
[...]
public async up(queryRunner: QueryRunner): Promise<void> {
await queryRunner.query(`ALTER TABLE "mercadopago_payment_request" ALTER COLUMN "succeededAt" SET DEFAULT null`);
[...]
It seems that Postgres treats null as the default value globally and doesn't require a specific rule for it. This confuses TypeORM, leading to unnecessary adjustments.
Do you have any suggestions on how to resolve this issue?
I attempted to remove the default value altogether:
@CreateDateColumn({
nullable: true,
type: 'timestamp',
})
public succeededAt?: Date;
However, this change results in a migration setting the default value to now():
export class migration123 implements MigrationInterface {
name = 'migration123';
public async up(queryRunner: QueryRunner): Promise\<void\> {
await queryRunner.query(
`CREATE TABLE [...], "succeededAt" TIMESTAMP DEFAULT now(), [...]`
);
\[...\]
}
I specifically need to set null as the default value, hence the initial configuration.