if you want to quickly select the link, while in browser, just press alt+d it and it will select whole URL. Works in File Explorer as well if you want to grab current path or navigate to address bar
Yea .. OData is such a great thing but no docs .. i mean how hard can in be to add/update docs? I am only using OData because i spent large amount of time playing with it to get full potencial of it When i am googling for something I always find out that its already deprecated even in their links from github repo .. i have ended up many times browsing their code to find my problem I get it that OData is still in development .. new features, breaking changes etc .. but updated docs would be really great for all of us who wants to use OData
YES! More docs Most of the demos / videos show extremely simple scenarios where "I have something IQueryable", or even worse: "I have EntityFramework which..." - - Sort of like the Windows Forms demos in 2002 where a lot of super-excited PMs all showed a DataGrid with editable rows over and over again, but then left you hanging when it came to the slightly harder things.
When people ask me what OData is that know .Net I tell them ... "LinQ over REST" ... when they don't know .Net I explain it like "secure db queries over REST". It's really hard to properly explain it though.
Yes, it is, this is why last time i said that in query capabilities i think Odata is more rich than GraphQL. in Tooling (cross techs and language) and community adoption graphQL is better. and this is where OData-Neo will shine!
Instead of offloading my db server I make it do more stuff. I dont like it. I want frontend do it. Also odata makes it easy for frontend devs kill db. You cant execute any possibile query and expect good performance.
Well, if you want the work on the client then make it happen on the client, but having the option is great, any server side dynamic query system (this, GraphQL) suffers from the same issue, the server does more work, but depending on what you need this is great
I would say ANY API can allow clients to kill the db and not just oData APIs. At the end it comes down to APIs general design principles and protecting backend serves from unruly requests
@@osman3404 I dunno, it’s hard enough to stop back end devs writing crap entity framework code and bringing SQL down with then adding yet another obfuscation layer on top of that.
![[DRIP] ‘Woke Up In Tokyo (RUKA & ASA)’ PREVIEW](http://i.ytimg.com/vi/QN44lcR_VkI/mqdefault.jpg)
I just love how Hassan is super enthusiastic about OData, his vibes are a better selling point than the tech :D
You just want to hear Hassan speak whenever he's Liv. Love you guys
i love how transparent this presentation is. thank you James and Hassan.
if you want to quickly select the link, while in browser, just press alt+d it and it will select whole URL. Works in File Explorer as well if you want to grab current path or navigate to address bar
I love this so much. Especially the projection = compute
hey I used to sit on the office next to Hassan's in MSFT. He is a cool dude
More docs, please. Lot more!
That's one thing that bugs me about using odata is the lack of updated documentation...
Yea .. OData is such a great thing but no docs .. i mean how hard can in be to add/update docs?
I am only using OData because i spent large amount of time playing with it to get full potencial of it
When i am googling for something I always find out that its already deprecated even in their links from github repo .. i have ended up many times browsing their code to find my problem
I get it that OData is still in development .. new features, breaking changes etc .. but updated docs would be really great for all of us who wants to use OData
YES! More docs
Most of the demos / videos show extremely simple scenarios where "I have something IQueryable", or even worse: "I have EntityFramework which..." - - Sort of like the Windows Forms demos in 2002 where a lot of super-excited PMs all showed a DataGrid with editable rows over and over again, but then left you hanging when it came to the slightly harder things.
Very cool stuff!
Loved Hassan's energy!
been using Odata a lot at my companies api's really nice to see the developers exited about it too :)
A lot of fun, thank hasan. You are passionate person
Simplemente ¡hermoso! ¡Gracias!
Thank you Hassan!
Hassan is great!
both of you are always enjoyable, thanks for the session!
Wow very impressive
This is amazing👊
Sweet!
It's really cool 😎
@Hassan Habib, where can we learn more about the concept of 28:00 lake house or substrate?
Thanks
Really cool man!
If I use EnableQueryFeatures() is there a performance downside (when not using everything)? Or would it be better to enable one by one if needed
No performance downside.
"Hey Frontend, you need an new endpoint for this?" Nah fam we got this. Backend out of job :( /s
Really liked you did the demo in Visual Studio (not VsCode). Thanks!
When people ask me what OData is that know .Net I tell them ...
"LinQ over REST" ... when they don't know .Net I explain it like "secure db queries over REST".
It's really hard to properly explain it though.
Yes, it is, this is why last time i said that in query capabilities i think Odata is more rich than GraphQL. in Tooling (cross techs and language) and community adoption graphQL is better. and this is where OData-Neo will shine!
Can we use OData with minimal APIs?
Unfortunately OData is not supported in minimal APIs
Is odata a first class supported app yet or still in development?
Supported and running in production in some of the biggest enterprise-level systems around the world.
@@HassanHabib really? Do you have any testimonials?
Hi Team
Need to know proper way to write mstest unit test cases for odata controllers
Please help
Can I use OData Compute in .Net 5?
Instead of offloading my db server I make it do more stuff. I dont like it. I want frontend do it. Also odata makes it easy for frontend devs kill db. You cant execute any possibile query and expect good performance.
Well, if you want the work on the client then make it happen on the client, but having the option is great, any server side dynamic query system (this, GraphQL) suffers from the same issue, the server does more work, but depending on what you need this is great
I would say ANY API can allow clients to kill the db and not just oData APIs. At the end it comes down to APIs general design principles and protecting backend serves from unruly requests
@@osman3404 I dunno, it’s hard enough to stop back end devs writing crap entity framework code and bringing SQL down with then adding yet another obfuscation layer on top of that.