Upsert expects unique constraint for `OneToOne` columns which imply uniqueness already

I get this error:

An upsert requires conditions that have a unique constraint but none was found for conflict properties: original_response_id

For code like this:

import TypeORM from 'typeorm';
import { Response } from './response';

@TypeORM.Entity()
export class Archive {
	@TypeORM.PrimaryGeneratedColumn('uuid')
		id!: string;

	@TypeORM.OneToOne(() => Response, response => response.id)
	@TypeORM.JoinColumn()
		originalResponse!: Response;
}

		await this._archiveRepository.upsert(archive, [ 'original_response_id' ]);

I also tried changing 'original_response_id' to 'original_response' or 'originalResponse' and it did not help.

This is the line where error is thrown: https://github.com/typeorm/typeorm/blob/26581d0264268045496b43f7a0f338eb9f2b70cc/src/entity-manager/EntityManager.ts#L509-L511

[mostafa-hz]

Solution

If I change shop to shop.id it will work!

https://github.com/typeorm/typeorm/blob/26581d0264268045496b43f7a0f338eb9f2b70cc/src/entity-manager/EntityManager.ts#L506

in the code above it checks for col.propertyPath which in my case was shop.id.

I’m not sure if it is expected behavior. @joeflateau shouldn’t col.propertyPath replaced with col.propertyName or col.propertyAliasName?

[joeflateau]

@futpib I’ve found the metadata for the one-to-many’s unique indices. I have a fix in testing now