Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[bug] missing field `on_delete` in preview-6
See original GitHub issueAfter upgrading to preview-6, prisma2 lift save reports the following error:
thread 'main' panicked at 'Deserializing the database migration failed.: Error("missing field `on_delete`", line: 0, column: 0)', src/libcore/result.rs:997:5
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:7 (6 by maintainers)
Top Results From Across the Web
Nested delete doesn't work with onDelete: Restrict #12927
Bug description When using { delete: true } with an optional relation configured with onDelete: Restrict, the query fails with Foreign key ...
Read more >ForEach onDelete bug with TextField - Stack Overflow
I don't see how this is not a bug. Delete works fine with Text but not TextField. Fails with a Index out of...
Read more >Installed preview 6, then reinstalled preview 5 in UI for Blazor
preview 6 breaks things pretty badly with Telerik components. So I uninstalled it and reinstalled preview 5, but now I am getting errors:....
Read more >Error when trying to delete a node with nested fields using ...
I'm currently encountering an error when trying to delete a node. The node has a relation with another node which is one of...
Read more >What's New in EF Core 6.0 | Microsoft Learn
--verbose to see detailed information on what the command is doing. Use this option when including information in bug reports. Use dotnet ef...
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
I can confirm this
Update: Thanks for raising this issue, we missed this regression between preview-5 and preview-6 and this should have been mentioned in the release notes. We will take measures to make sure that we avoid that in future.
We expect breaking changes like these to occasionally pop up between preview releases and we will have release notes for all regressions. I will close this issue.
Please re-open a new issue if you feel that something is still unaddressed from this issue.