SEDE - Stack Exchange Data Explorer

« first day (572 days earlier) ← previous day next day → last day (3128 days later) »

6:25 AM

@MartinSleziak but that question was close voted yesterday so that didn't make it yet in SEDE.

@rene Hard to believe I am that stupid.

I have heard that SEDE is updated only once a week many times. And for some reason I have ignored this in this instance.

I have still doubts about the last sentence in your answer. At least if I understood it correctly. (As explained in the comment and also here in chat.)

But I am not sure where meta.stackexchange.com/questions/linked/267325 and meta.stackexchange.com/questions/linked/239619 are a counterexample.

I should find a question which was closed as a duplicate, but the link does not appear in comments/answers/questions neither in the duplicate question nor in the duplicate target to test this.

I.e. the situation where the only link between the two questions is the duplicate banner.

No, it means that if it gets closed as a duplicate it gets an record in postlinks as linktype=3, no need to be mentioned in a post or comment. The example you provided in chat was to recent to have that linktype=3 in SEDE as SEDE us only update once a week, on sunday morning 03:00 UTC — rene 12 mins ago

So just to see whether I understand it correctly.

In this particular instance there is one link with PostTypeId=1, because of the comment which was auto-generated when somebody voted to close the question.

This comment was removed in the meantime.

When data in SEDE are updated there will be link with PostTYpeId=3, since it is closed as duplicate.

I assume that the link with PostTypeId=1 will be removed. (Since the comment no longer exists.)

I understood this sentence: Only the direct links are shown in the list. like this: If there is only a link with PostTypeId=3 between two posts and no link with PostTypeId=1, then the questions will not be shown in the list of questions generated by http://meta.stackexchange.com/questions/linked/id.

Maybe this is not what you meant.

rene

6:51 AM

@MartinSleziak I didn't mean to give you the impression you are stupid, sorry about that.

Martin Sleziak

@rene I did not say that you wanted to give that impression.

You certainly did not say anything that would be offending to me. On the contrary, you were very helpful.

rene

@MartinSleziak You'll find such counter examples. For example if a comment was removed that Created the row, the postlink table is not updated

Martin Sleziak

But I am surprised that I encountered the fact that updates are done only once a week and I did not think that this could explain the apparent dicrepancy.

rene

@MartinSleziak No, I don't think that will happen

Martin Sleziak

@rene So in this particular case after the update there will be two rows with 3 and 1. Even if the only place linking between the two posts is a duplicate banner.

rene

6:54 AM

Yes, that is how I understand and understood that functionality

Martin Sleziak

And again in this particular instance even if the duplicate banner is the only place which links between the two questions, they will be still shown in meta.stackexchange.com/questions/linked/267325 and meta.stackexchange.com/questions/linked/239619 - in the list generated by url of the form http://meta.stackexchange.com/questions/linked/id

rene

Yes, because due to the duplicate vote the generated comment will immediately generate a type 1, the type 3 gets recorded if the question gets closed with a majority vote for the dupe

brb

Martin Sleziak

Ok, so it seems that I simply misinterpreted what you meant by the last sentence of your answer.

I think that the issue is cleared up.

It can be still probably considered a bug, but it is certainly not a big problem.

rene

7:15 AM

@MartinSleziak OK, I'll try to rephrase that so it gets more clear and that might also trigger some one who actually has access to the code can verify if my reasoning matches the implementation.

Martin Sleziak

Thanks once again for your time.

I will wait a bit before accepting the answer. Just in case some SE developer will add confirmation that it indeed works this way.

rene

@MartinSleziak that sounds as a good idea. I don't want to share information that turns out to be wrong.

rene

7:30 AM

@MartinSleziak updated the answer a bit

Martin Sleziak

Thanks. I will have a look

« first day (572 days earlier) ← previous day next day → last day (3128 days later) »

all rooms