@PaulWhite You mean I get to explain? At great length?? Sqweeee!
Yeah, so it's not "a horse walked into a bar" funny, but it made me grin. And it hit enough of the tropes of this audience that I thought I would share.
But as it stands, it looks like an arrogant person assuming the beginners are too stupid to understand whatever it was they did to speed the query up. At the very least, the "wizard" is making no effort at all to benefit anyone except themselves.
He probably turned on Query Store and pinned a fast execution plan.
Nerd.
Good Morning
Seems like Query Store and AI in SQL 21019 is going to be the solution to my growing database issues I have been ranting about.
You just can't tune LIKE '%VALUE%'and if the statistics change because tables do grow, then you are basically just F * C K * D when the query execution plan changes.
What is the correct name anyway? A) Query Plan B) Query Execution Plan C) Cached Query Execution Plan D) Query Store Cached Execution Plan E) Query Store Cached Query Execution Plan
So I have this Q and somebody else had a nice A. Didn't exactly solve my issue, but put me on the right track. I upvoted their answer and was prompted immediately by the site to consider marking the answer as Accepted - but it wasn't the correct answer...
So I went on and solved my problems. Came...
@PaulWhite After thinking a bit more about this, perhaps the author is simply taking the mickey out of the idea that queries could become faster by magic, or the desire that an ignorant dev might have that that were the case. As in, "Oh, I don't know what else I can do. If only there were some kind of magic to make this query faster!" Intuitively this seems close to what I perceive the joke to be about, though it's still hard to deconstruct it precisely (as is often the case with jokes).
@AndriyM Well yes there are any number of ways a joke could work there. For example, the query could be faster due to the data being cached after the first run, but it seems unlikely the two original participants wouldn't have tried that. So, idk.
I guess I am from a time where cartoons were funny in an obvious kind of a way
In this answer, I attempt to add a link with a "scroll-to-text" anchor
https://www.postgresql.org/docs/13/release-13.html#:~:text=Allow%20ROW%20expressions%20to%20have%20their%20members%20extracted%20with%20suffix%20notation
That exact link should take you about halfway down the page and display ...
Percent-encoding, also known as URL encoding, is a method to encode information in a Uniform Resource Identifier (URI) under certain circumstances.
Although it is known as URL encoding, it is, in fact, used more generally within the main Uniform Resource Identifier (URI) set, which includes both Uniform Resource Locator (URL) and Uniform Resource Name (URN). As such, it is also used in the preparation of data of the application/x-www-form-urlencoded media type, as is often used in the submission of HTML form data in HTTP requests.
== Percent-encoding in a URI ==
=== Types of URI charact...
The linked section lists ~ as one of common characters using percent encoding
Oops, sorry, I may have misread that
The actual wording is slightly different, so maybe ~ isn't (supposed to be) always encoded
My take on the cartoon is your typical devs are a bit clueless on how databases work, but really I feel like it's the job of any good DBA/database developer/"data engineer" to show others how to do things right. So I was somewhere in between @PaulWhite and @MichaelGreen in terms of appreciation.
@PeterVandivier Have you noticed the link works correctly in preview? Edit your answer, and click the link in the preview window (do not submit any edit).
It will probably help the dev that looks at your issue if you update it to be clear, concise, and include all the latest information you have. I see quite a lot of extra detail floating around here and TA.
> Additionally, the fragment will activate only if the document is sufficiently isolated from other pages (is the only one in its browsing context group, e.g. no window.opener or iframes).
I ran your post through MarkdownSharp and the tilde was not encoded during the rendering from markdown to HTML. So the problem is likely elsewhere on the server side. Hopefully an SO dev will come along and check on this. The tilde doesn't need to be encoded in a URI, since it's an unreserved ...