Ash.bulk_create/4 returns empty list records when using integer primary keys

[nallwhy]

Code of Conduct

• I agree to follow this project's Code of Conduct

AI Policy

• I agree to follow this project's AI Policy, or I agree that AI was not used while creating this issue.

Versions

elixir 1.18.3
erlang 27.3
ash 3.6.2
ash_postgres 2.6.22

Operating system

mac

Current Behavior

Starting from ash_postgres 2.6.22, calling Ash.bulk_create/4 returns empty list records even when the insert actually succeeds in the database.

This regression seems related to the following commit:
af0903f

From the code changes, it appears that the new identity-based result matching logic introduced in this commit fails when the primary key is integer-based (auto-increment), since the key is not present in the input changesets.

Reproduction

No response

Expected Behavior

No response

[zachdaniel]

😓 Of course. I didn't think of this.

[zachdaniel]

@nallwhy 🤔 actually, is this happening just from a regular bulk create or only on a bulk upsert? Could you show me an example?

[zachdaniel]

On a bulk upsert where this code was added, it should be the case that the upsert keys are present in the input. Are you sure you didn't forget return_records?: true