I have tested this using .net 4.8 and Core 3.1 against Sql Server, they all exhibit the same problem.
The best course of action is probably to identify a workaround, based on your project, until Microsoft team have the time to fix the issue. It would be good idea to report this to Microsoft.
On 2/11/20 8:35 AM, Vikram Sah wrote: > Got it sir, but unfortunately they have not provided any solution for > the last 5 days.
Where have you asked besides here?
> > Thanks > > On Tue, 11 Feb 2020, 10:12 pm Adrian Klaver, <adrian.klaver@aklaver.com > <mailto:adrian.klaver@aklaver.com>> wrote: > > On 2/11/20 3:56 AM, Vikram Sah wrote: > > Thank you so much sir, but it didn't work for me as the database > > function in PostgreSQL and EntityFramework6.Npgsql is used as > provider > > for entity framework. > > I have no idea where to go from here. Your best bet would be to reach > out to the EntityFramework6.Npgsql community > > > > > Thanks! > > Vikram > > > > > -- > Adrian Klaver > adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com> >