Question shrunk since the issue is known and will be addressed in due time. (View complete question.)

Error in SEDE when using magic column: error

  • Example #1: Control query (no magic column).
  • Example #2: Example #1 + added automated magic column [Post Link]
    - queries 7 days back without error
    - change parameter to 10 or more to reproduce error.

  • Example #3: Example #1 + added custom column[My Post Link]
    - same functionality as '[Post Link]" using an additional join. (Runs properly.)

Similar question:
- Out-of-resources when trying to run a popular DataExplorer query (known issue <=2016)

Workaround Links:
- 'site://posts/' + cast(id AS nvarchar)+'|'+title as [Alt. Post Link]
- 'site://users/' + cast(userid as nvarchar) as [Alt. User Link]
(Source: @Rene)

  • 1
    I don't understand why you say the workaround I offered doesn't apply while you still use that workaround to overcome the issue. Unless I miss something this question is a duplicate of that question where I wrote my answer. As for hasn't been addressed is correct but obviously no-one seems interested enough to submit a PR on the GitHub repo to solve it. This needs a community member to fix, not SE staff. – rene Apr 6 '18 at 9:26
  • @rene funny - looking at your post again I realize I saw your workaround, dismissed it, wrote my post, and then came up with the same workaround on my own...anyhow I rephrased & no offence was intended, it was meant to give you credit for being the only other user who's attempted to address this. ...I didn't realize there was a PR process on GitHub. Is it specific to SEDE? And why can't staff be involved? – ashleedawg Apr 6 '18 at 9:32
  • 1
    SEDE is open source. It is only hosted (and seeded with data) by SE. Although staff are free to offer code (and some have done) the development of SEDE and fixing bugs is not on their priority list, at all. Although if you submit an PR you have to be ready to have it code-reviewed by Nick... – rene Apr 6 '18 at 9:42
  • Very cool; I had no idea. I assumed it was a 3rd party "plugin" for the site. – ashleedawg Apr 6 '18 at 10:33
  • 1
    @rene Yeah, that's my bad (as usual). I have a fix for this somewhere, I just needed to test it...will do so and then put a PR out – Tim Stone Apr 6 '18 at 12:19
  • 1
    @TimStone not trying to make you feel bad. I'm happy to help / assist if/when you see fit. Just ping me ... – rene Apr 6 '18 at 12:53

You must log in to answer this question.

Browse other questions tagged .