Preview feature feedback: Prisma field reference support (`fieldReference`)

Please share your feedback about the fieldReference functionality released in v4.3.0 in this issue.

• If you encounter a bug, please open a bug report in this repo.
• If the feature is working well for you, please share this in a comment below or leave a 👍 on this issue.

If you have any questions, don’t hesitate to ask them in the #prisma-client channel in the Prisma Slack.

[shtse8]

hope it can do it with cross models. A.updatedAt > B.updatedAt

[matthewmueller]

Request for references across tables from @danshapir:

Assume we have 2 tables. Accounts and Transactions We have a field on the Accounts called LinkTime, a datetime. We want to find all transactions where their createdAt is larger than the LinkTime of their parent account.

That’s for the simple query, just comparison of fields from a join. For the more complex scenario, but something we all do a thousand times using SQL, we create a dynamic property as part of the select (computed of multiple fields or any other logic, or maybe aggregated SUM/MIN) and we want to only fetch items that are larger or equal to it.