Getting error on deeper includes
See original GitHub issueI am getting this error on Preview 23 that worked on Preview 21 Error:
Expected at most 1 item for 'timetable', got 2
Query:
const data = await prisma.passenger.findMany({
include: {
booking: {
include: {
timetable: true
}
}
}
});
Issue Analytics
- State:
- Created 4 years ago
- Reactions:5
- Comments:22 (9 by maintainers)
Top Results From Across the Web
Troubleshooting - Deeper Support
If you're getting the "too shallow or too deep" error message, first of all check if the depth you're fishing at is sufficient...
Read more >Connection issues with Deeper's Wi-Fi
Open the Fish Deeper application and connect to your Deeper. Note: When connecting over Wi-Fi, you may see an error “no internet connection”...
Read more >Solved: Error in import solution when the resources contai...
Solved: I've created a pcf component having in the manifest the following resources: This worked before upgrading the pac tool.
Read more >FIXED: Minecraft Error Code Deep Ocean | Working Tutorial
Error Code: 0x80070057 code: Deep Ocean. Something went wrong in the login process while trying to run the game.Minecraft launcher Error ...
Read more >Fix the 'Communication Problem Detected' error message
Product/Version includes:Deep Security 10.0, View More. Update Date: 2019/09/09 ... Once in the console, press ALT+F2 to get to the console login screen....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
+1
I am also seeing themissing FROM-clause
error when trying to include a field that is part of a M-N relation. It was working fine in preview022Ah, Should have checked that. I just installed @latest. Anyways, installed the alpha and ran a couple queries that I knew would break and they now work! Nice work!!