In the vast, uncharted wilderness of the living room, a pioneering white rat, equipped with high-tech GPS gear, embarks on a valiant expedition. The objective? To chart the perilous route to the mythical cardboard box. On the sidelines, a perplexed human, wrapped in his blanket of ignorance, silently observes. Unbeknownst to him, he is witnessing a monumental moment in rodent exploration, a tiny pioneer bravely navigating the domestic jungle. Here, in the humble living room, history is written by those who dare to scurry.
Skill issue. Old version docs tend to offer you a redirect to more recent docs, and even then something sintactic like an “IN” operator is unlikely to change in form or structure between versions of a database engine.
Old version docs tend to offer you a redirect to more recent docs
Sadly, the docs, I’ve worked with (openstack and ansible) frequently, don’t do this. They have a button to go to the latest version of the docs, but not to the equivalent page on the latest version. This means I have to find the equivalent page again, from the integrated search usually.
And yes, a lot can change between versions. New features can get added that solve your problems or older stuff can get removed.
You didn't include a version in your query. You also could try using quotes, though this specific entry may not be helped by it (e.g. "in operator"). For most things, you can click a link with the older version and somewhere there is typically a dropdown or something to change the version and, if not, you'll at least know which section/etc. it is in in the new documentation.
If you don't include a version, it's probably going to pull up questions/answers that it finds most match in general and maybe people just aren't asking that question for your version.
I think there's a lot to hate about modern search results, but I also think there's some opportunity to search better. I do miss the days when AND, OR, and NOT operators actually worked all the time and as expected.
sopuli.xyz
Top