-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature like query tags but when calling SaveChanges #14078
Comments
Just wanted to check and see if there's been any progress on this? I have a similar situation where something like this would be really useful. I need to modify an insert statement for certain tables, but _context.DbSet.TagWith("-- Use hint: insert").AddRange(items);
public override ValueTask<InterceptionResult<DbDataReader>> ReaderExecutingAsync(
DbCommand command,
CommandEventData eventData,
InterceptionResult<DbDataReader> result,
CancellationToken cancellationToken = default)
{
if (command.CommandText.StartsWith("-- Use hint: insert", StringComparison.Ordinal))
{
// Do something with the insert command
}
return base.ReaderExecutingAsync(command, eventData, result, cancellationToken);
} |
@RKennedy9064 You could try setting an AsyncLocal field on the context in SaveChanges, and then check it in the interceptor. |
One way to handle this is by adding some tags/fields to your datacontext, and then checking those tags/fields in the appropriate interceptor method ... see below. You can then use twiddle with your sql all you want. Just set these tags/fields on your datacontext before calling SaveChangesAsync.
|
I just setup a basic extension method that adds the calling file's path & line number as a tag to the given query:
This works fine when querying for data, but I'd also like it to be part of the queries that execute when calling
db.SaveChanges()
. Is this possible currently? Adding query tags to updates is just as important, if not more important with this one, than adding them to selects.The inspiration for this came from Stack Overflow who prepends this info to every query that runs through Dapper https://gist.github.com/NickCraver/c6f371bf8df37e05c4f09fd3c02ef6a2
What I really like about this is when using MiniProfiler this info becomes available making debugging easier. Then taken a step further it's included in Sentry's breadcrumbs that are part of logged exceptions, and it's also passed into App Insights. Both of those scenarios make production issues easier to track down.
Further technical details
EF Core version: 2.2.0
Database Provider: Microsoft.EntityFrameworkCore.SqlServer
Operating system: Win10
IDE: Visual Studio 2017 15.9.3
The text was updated successfully, but these errors were encountered: