Two things ye shall know
Hint: One is a C# thing, and the other is a SQL thing :)
Yep, that is me every time I open my code editor these days!
I am no longer a real everyday coder and perhaps I never was! Talk about imposter syndrome! (no affiliation, but a worthy book IMHO!). I like Rob Connery's style and have watched or read a few things from him over the years :) Oh, and once again, I am not earning anything from this. If you want to delve deeper into “data” and Postgres, then I am definitely going to have a read of a curious moon.
Right, where was I…
Two things ye shall know - well from a quick filtering of what jumped out on my weekend reading list anyway!
Being a tad more efficient with SQL queries when joining - not using the DISTINCT keyword :)
This seemed very appropriate of late since I have had a couple of queries where I did cheat and added a distinct to stop multiple rows of the same customer from being repeated.
Good old Aaron Bertrand over on the Redgate hub has a really clean example of how to achieve the above-mentioned query WITHOUT any distincts… as these distincts do, over time with large amounts of data, really do start to diSTINCts. Darn this trying to add humour into these posts! (sorry, humor if you can’t read English ;) ).
Guarding all the dotnet things…
Another intriguing read (don’t worry, not more than 5 mins!) is about “Guard Clauses” which I am guessing are not related to “Santa Clauses” :) hey, I don’t get paid for quality humour! and as of the time of this writing, Christmas isn’t far away.
Steve Smith “Ardalis” has a really good intro to how and why guard clauses are useful in your C# classes - I suppose most languages. Instead of hefty IF conditions littering your code, why not try the bouncer method? If you ain’t got the right data, you ain’t coming in.
Anyway, this might not be too useful, but “talk to the unicorn, the face don’t wanna know!” :)
Until next time!