Fix TypeORM errors for nullable fields

For fields with '| null' in the TS type, the column type needs to be
specified explicitly in column options when using MySQL.

See:
https://github.com/typeorm/typeorm/issues/1358#issuecomment-391736766
This commit is contained in:
Dragory 2020-11-09 20:11:33 +02:00
parent 629002b8d9
commit 2f50232cf3
No known key found for this signature in database
GPG key ID: 5F387BA66DF8AAC1
6 changed files with 14 additions and 14 deletions

View file

@ -13,27 +13,27 @@ export class Case {
@Column() user_name: string;
@Column({ nullable: true }) mod_id: string | null;
@Column({ type: String, nullable: true }) mod_id: string | null;
@Column({ nullable: true }) mod_name: string | null;
@Column({ type: String, nullable: true }) mod_name: string | null;
@Column() type: number;
@Column({ nullable: true }) audit_log_id: string | null;
@Column({ type: String, nullable: true }) audit_log_id: string | null;
@Column() created_at: string;
@Column() is_hidden: boolean;
@Column({ nullable: true }) pp_id: string | null;
@Column({ type: String, nullable: true }) pp_id: string | null;
@Column({ nullable: true }) pp_name: string | null;
@Column({ type: String, nullable: true }) pp_name: string | null;
/**
* ID of the channel and message where this case was logged.
* Format: "channelid-messageid"
*/
@Column({ nullable: true }) log_message_id: string | null;
@Column({ type: String, nullable: true }) log_message_id: string | null;
@OneToMany(
type => CaseNote,