I was asked about this in another room.

I have suggested to use the list of linked questions as a quick way to find some approximation of the list of duplicates.

I have also tried some queries using the PostLinks table: Duplicates of the given post, Duplicates of the given post (only not deleted) and ...

... Duplicates of the given post (only deleted)

If somebody has some time to look at them and have some suggestions for improvements or for other ways to do that, let me know.

> CloseAsOffTopicReasonTypeId, *if CloseReasonTypeId = 102 (off-topic) (listed in the CloseAsOffTopicReasonTypes table).

Several places in "Database schema documentation for the public data dump and SEDE" link to this query: Show all types

However, from that query I get the error: "Invalid column name 'MarkdownMini'."

@Martin Hmm, we need Gilles to fix that

I'm sure I have chatted about that query earlier

Okay I found the old room.

trying to get it unfrozen

that part has succeeded: chat.stackexchange.com/transcript/message/54367436#54367436

Are there actually that many posts which link to this query?

Posts on Meta Stack Exchange: search for url:"data*36599"

Comments on Meta Stack Exchange containing 36599.

Okay, maybe I'm trying to hard to not step on people toes ...

that query is 18 times favorites.

Well, you'll see whether Gilles responds.

If the correction can be done without having to correct link in all places, it is definitely better.

Especially, it is not easy to edit links in comments.

I always forget that when I am using Stack Exchange search, I can actually search over all sites.

For comments it would be more difficult for me - I have no experience with multisite queries in SEDE.

Comments might be tricky to do networkwide. that are many, many rows.Way more then posts

@Martin I have not much to add but had some fun with using the Posthistory table to get that same data: data.stackexchange.com/math/query/1238008

@Martin he did, solved!

Indeed, the "Show all types" query now works.

Thanks for looking at the duplicate targets. The fact that in PostHistory several ids are in one JSON string is the reason why I was trying that with using the PostLinks table.

Yeah, I think there is no real benefit for using the posthistory for this case, unless you also want to know the close voters.

PostLinks is a much better venue for that