Fixed potential guild message SQL constraints
i have tied member dependencies to the author id rather than the member id to avoid a dependency cycle and you can now kick/ban someone from a guild/server and the messages will remain in the guild (just like discord) as stated in issue #441 I have also tested this code seems clean so far (new pull request opened because of branch commit issues)
This commit is contained in:
parent
f132065664
commit
716ea8b233
@ -84,8 +84,10 @@ export class Message extends BaseClass {
|
|||||||
@RelationId((message: Message) => message.member)
|
@RelationId((message: Message) => message.member)
|
||||||
member_id: string;
|
member_id: string;
|
||||||
|
|
||||||
@JoinColumn({ name: "member_id" })
|
@JoinColumn({ name: "author_id", referencedColumnName: "id" })
|
||||||
@ManyToOne(() => Member)
|
@ManyToOne(() => User, {
|
||||||
|
onDelete: "CASCADE",
|
||||||
|
})
|
||||||
member?: Member;
|
member?: Member;
|
||||||
|
|
||||||
@Column({ nullable: true })
|
@Column({ nullable: true })
|
||||||
|
Loading…
x
Reference in New Issue
Block a user