Arthur Vickers
Arthur Vickers
Consider only using openjson for types that are going to be truncated (`nvarchar(max)` and `varbinary(max)` or where we need the conversion to/from base64 (`binarty` and `varbinary(x)`).
We discussed this, but it is out-of-scope for the EF tool to handle all of this.
@vallgrenerik I think if we were going to work on this, then it would mostly about providing better messages in cases where it doesn't work, such as changing a query.
@bytefish Unfortunately, the EF team does not have any time available to spend on this at the moment. /cc @SamMonoRT
> if usage of the DbContext, as suggested in this TransactionBehavior, is best practice? No, in general this repo should not be used for guidance on how to use EF...
@adityamandaleeka No, this is a longer-term thing. We have to decide what to replace it with.
@adampaquette This fix is not included in 7.0.2. Check the milestone on the issue.
Ah sorry, missed that. The version of the CLI tool doesn't usually matter. Make sure your project is using the latest daily build packages.
@Sebazzz Please open a new issue and attach a small, runnable project or post a small, runnable code listing that reproduces what you are seeing so that we can investigate.
Adding a note to help me find this in the future; fully-qualified typed for compiled model. :-)