ASP.NET Core: A powerful API Design with OData, EF and SQLKata

I will cover everything under REST API design.

API Design

Projection

You might say, each entity should be separate and live apart. In this case, you might think like your database system is old, big and growth uncontrolled. Thus, SQL View could help with your needs.

UPDATE [Country_Songs] SET [Status] = @p0 WHERE [SongId] = @p1

Conclusion

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store