Debug Your Infrastructure
Get Instant Solutions for Kubernetes, Databases, Docker and more
Javascript TypeORM Encountering the NoVersionOrUpdateDateColumnError when using TypeORM.
Understanding TypeORM
TypeORM is a popular Object-Relational Mapper (ORM) for TypeScript and JavaScript (ES7, ES6, ES5). It is designed to work with various databases like MySQL, PostgreSQL, MariaDB, SQLite, and more. TypeORM allows developers to interact with a database using TypeScript or JavaScript classes and provides a powerful abstraction over raw SQL queries.
For more information, visit the official TypeORM website.
Identifying the Symptom
When working with TypeORM, you might encounter the NoVersionOrUpdateDateColumnError. This error typically appears when you attempt to use optimistic locking in your application.
What You See
The error message will look something like this:
Error: NoVersionOrUpdateDateColumnError: Entity "YourEntityName" does not have version or update date column.
This indicates that TypeORM is unable to find a version or update date column in the specified entity.
Explaining the Issue
The NoVersionOrUpdateDateColumnError occurs when optimistic locking is enabled on an entity, but neither a version column nor an update date column is defined. Optimistic locking is a technique used to ensure data consistency by preventing concurrent updates from overwriting each other.
Why It Happens
Optimistic locking requires a mechanism to detect changes. This is typically done using a version column (an integer that increments with each update) or an update date column (a timestamp that updates with each change). Without these columns, TypeORM cannot track changes, leading to the error.
Steps to Fix the Issue
To resolve the NoVersionOrUpdateDateColumnError, you need to define a version or update date column in your entity. Here are the steps:
Step 1: Define a Version Column
Add a version column to your entity using the @VersionColumn decorator. This column will automatically increment with each update.
import { Entity, PrimaryGeneratedColumn, Column, VersionColumn } from "typeorm";
@Entity()
export class YourEntity {
@PrimaryGeneratedColumn()
id: number;
@Column()
name: string;
@VersionColumn()
version: number;
}
Step 2: Define an Update Date Column
Alternatively, you can use an update date column with the @UpdateDateColumn decorator. This column will automatically update its timestamp with each change.
import { Entity, PrimaryGeneratedColumn, Column, UpdateDateColumn } from "typeorm";
@Entity()
export class YourEntity {
@PrimaryGeneratedColumn()
id: number;
@Column()
name: string;
@UpdateDateColumn()
updatedAt: Date;
}
Conclusion
By defining either a version column or an update date column, you enable TypeORM to manage optimistic locking effectively, thus resolving the NoVersionOrUpdateDateColumnError. For further reading on optimistic locking, refer to the TypeORM documentation on optimistic locking.
Master
Javascript TypeORM Encountering the NoVersionOrUpdateDateColumnError when using TypeORM.
debugging in Minutes
— Grab the Ultimate Cheatsheet
(Perfect for DevOps & SREs)
Javascript TypeORM Encountering the NoVersionOrUpdateDateColumnError when using TypeORM.
Cheatsheet
(Perfect for DevOps & SREs)
MORE ISSUES
Backed by
