Skip to content
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

Are Query Notifications on the roadmap? #17168

Closed
rposener opened this issue Apr 29, 2016 · 16 comments
Closed

Are Query Notifications on the roadmap? #17168

rposener opened this issue Apr 29, 2016 · 16 comments
Assignees
Labels
area-System.Data.SqlClient tenet-compatibility Incompatibility with previous versions or .NET Framework
Milestone

Comments

@rposener
Copy link

It seems the System.Data.SqlClient does not include any of the query notification (SqlNotification or SqlDependency) classes. is this on the roadmap to be added?

@ViktorHofer
Copy link
Member

ViktorHofer commented Apr 14, 2017

@saurabh500 @YoungGah @karelz It seems we still haven't ported them to corefx. Any reason why? I see them supported in Xamarin and Desktop: https://apisof.net/catalog/System.Data.SqlClient.SqlDependency

@karelz
Copy link
Member

karelz commented Apr 14, 2017

@corivera any insight here?
@stephentoub @weshaggard @danmosemsft?

@akoeplinger
Copy link
Member

@ViktorHofer FYI it's just a stub in Mono/Xamarin at the moment: SqlDependency.cs

@ViktorHofer
Copy link
Member

@karelz Moving this to future as we reached feature freeze...

@karelz
Copy link
Member

karelz commented Apr 16, 2017

I'd like area experts & owners to make the decision. While we are past feature complete, there are options like DCRs, etc. I would prefer to focus on doing the right thing for the customers rather than process.

That said, given they are stubbed out in Xamarin, it feels more like Future to me as well, but I don't have enough background in the space to make the call ...

@corivera
Copy link
Member

We currently don't have any plans for working on query notifications.

@grahamehorner
Copy link

Is there any mileage in possibility providing a work around until officially supported, this is a blocker for us moving to asp.net core as we aren't able to invalidate cached items as notifications was used as the trigger this

@saurabh500
Copy link
Contributor

Query notifications via SqlDependency and related APIs is a feature we have on the backlog. However we couldn't get it into 2.0 because we didn't have the bandwidth.
We will be looking to port this feature in Future iterations.

@saurabh500
Copy link
Contributor

@maike9
Copy link

maike9 commented Jun 11, 2017

This is a roadblock to moving to .net core for me too.

@saurabh500
Copy link
Contributor

saurabh500 commented Jun 12, 2017

@maike9 What is your scenario for query notification?

@corivera
Copy link
Member

Query notification support was added in dotnet/corefx#20708

@ViktorHofer
Copy link
Member

... and will be available with the .NET Core 2.1 and the next version of UWP. Right @corivera ?

@corivera
Copy link
Member

Yep

@ChristopherRobinSuperStar

@corivera Is it possible to use it with action attribute in asp net core 2.1?
Before in asp net mvc it was:

[OutputCache(Duration = Int32.MaxValue, SqlDependency = "DBNAME:DEPENDENCY_TABLE_NAME", Location = System.Web.UI.OutputCacheLocation.Server)]
public ActionResult Index()
{
}

@karelz
Copy link
Member

karelz commented Jun 1, 2018

@msftgits msftgits transferred this issue from dotnet/corefx Jan 31, 2020
@msftgits msftgits added this to the 2.1.0 milestone Jan 31, 2020
@ghost ghost locked as resolved and limited conversation to collaborators Dec 31, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-System.Data.SqlClient tenet-compatibility Incompatibility with previous versions or .NET Framework
Projects
None yet
Development

No branches or pull requests