@connection directive doesn't create an one-to-many relationship using primary key.

Describe the bug @connection directive doesn’t create an one-to-many relationship using primary key.

To Reproduce

1. Create two types (account and book) at schema.
2. Account uses @key to declare userId as its simple primary key.
3. Book uses @key to declare userId and createdAt as its composite primary key.
4. Account uses @connection next to its books field to connect with book type with “userId” as primary key.
5. Create an account followed by creating a book using the same userId .
6. Query account and its books field shows null.

type account
	@model
	@key(fields: ["userId"])
	) {
	userId: String!
	books: [book] @connection(fields: ["userId"])
}

type book
	@model
	@key(fields: ["userId", "createdAt"])
	) {
	userId: String!
        createdAt: String!
	title: String
        author: String
}

Expected behavior When account is query, it’s books field should show the book created.

[xitanggg]

I just checked. This issue has been resolved sometimes ago (idk by which commit). The documentation also makes a note If keyName is not provided, then @connection queries the target table’s primary index. Good work Amplify team!

[github-actions[bot]]

This issue has been automatically locked since there hasn’t been any recent activity after it was closed. Please open a new issue for related bugs.

Looking for a help forum? We recommend joining the Amplify Community Discord server *-help channels for those types of questions.