56

Is it possible to delete or at least hide your own data explorer query when you know you've only been testing something and don't want it to show?

  • 3
    I am new to Data Explorer and today edited the same query a few times. Now I found that older versions of the same query are stored as separate ones in my profile data.stackexchange.com/users/8597/michael-freidgeim. It is confusing and it should be an ability to remove the draft versions of the same query. – Michael Freidgeim Jun 8 '13 at 9:55
  • 6
    While you're trying to figure out the right syntax and column names it seems to permanently publicly archive every tweak. I avoid ever writing any queries on the Data Explorer because of that exceptionally stupid behavior, and instead have to hope there is already a query that does what I want, but oh wait, I won't find it if there is one because there's a thousand other queries with hard-coded single-use values sitting around, that someone used three years ago one Tuesday afternoon. It's awful. – Boann Jun 8 '14 at 19:34
15

No, you cannot currently hide queries that you've ran, but better query organization tools are on the todo list that will hopefully address this and other concerns.

We keep track of all executed queries to monitor for abusive behaviour, so following any changes you'd only be able to at most "hide" them (similar to deleted posts here), but from the user perspective that should amount to the same thing.

Just to clarify, since people keep commenting about it – this is on the todo list, just be patient.

  • 2
    Well using data explorer you can test whatever query even creating your own temporary data that hasn't got anything to do with any of the StackExchange site. This means that you can write some queries that you don't wan't to be public. – Robert Koritnik Feb 14 '12 at 12:10
  • 2
    Arguably in that case the solution is just "Don't do that", then. – Tim Stone Feb 14 '12 at 12:19
  • 14
    Another reason is also that not all queries are usable or even valid. Some of them are worse duplicates that were superseded by a better variant. Take these two for example: a better version and a previous worse one. The better version has all the data plus average data. I would be glad to delete the worse version. Why I created two of them is a different Q but this likely happens to others as well. – Robert Koritnik Feb 14 '12 at 12:19
  • 4
    Basically just like questions and answers can be deleted so could be these. Or voted to be closed as duplicates or similar. – Robert Koritnik Feb 14 '12 at 12:21
  • 1
    I am actually interested in why you created two queries instead of just revising the first one, in case it indicates a problem with the workflow. As far as hiding queries goes, I'm still not really a fan of the idea for various reasons, though waffles may feel differently. – Tim Stone Feb 14 '12 at 12:36
  • 13
    The real answer is Lack of experience with data explorer so I opened the same thing in the other browser comparing results... I know, but I consider myself an average user, so I suppose this is not a seldom thing. Hence the close/hide/delete feature question. – Robert Koritnik Feb 14 '12 at 23:23
  • 5
    For some personal reason, I really want to delete queries I have written. It's counter-intuitive that I don't have the right to delete what I create – Hoàng Long Apr 8 '13 at 22:48
  • 5
    I wish to delete my queries, because I was playing with someone else query, and didn't realize I created "revisions" of his query, it just feel wrong that those queries are available to anyone while it was just learning DB schema. I believe each query run should be private, and only those explicitly "saved" (no option as of today) or those "created" should be available to public after establishing a good query title – Pawel Cioch Dec 5 '13 at 19:49
  • 3
    Some people just dislike clutter. It's the reason git has --amend, Gmail (eventually) added Delete in addition to Archive, and Macs have so few ports on the side. – duozmo Apr 29 '14 at 23:36
  • 2
    If you want to keep track of executed queries, log them on your side, and delete old logs after 60 days or something. It's not useful to permanently archive and display old broken/junk/test/single-use queries for everyone else. – Boann Dec 26 '14 at 22:24
  • Has this been implemented? I came to ask the same question but didn't want to create a duplicate. – Raystafarian Jan 31 '16 at 10:45
  • 2
    "this is on the todo list" - is this still the case? Or can this be marked as status-declined so people won't build false hopes? – Shadow The Dragon Wizard Nov 18 '16 at 21:33
  • ANy News about its availability still? – T.Todua Sep 7 '17 at 7:57
  • 1
    I've started renaming my old queries [Deleted] to get around this, although it just gives me a load of queries called [Deleted] – jrtapsell Feb 1 '18 at 12:13
10

No, you cannot, but you can edit the name and description so as to no longer be meaningful (e.g. Name = "Delete me", Description = "select 1").

  • 2
    I used an empty name and I added a comment -- DELETE THIS QUERY as description. At least I see empty lines in edited section on my profile. – ROMANIA_engineer Dec 24 '15 at 18:44
  • It is important to note that if you forked someone else's query, edited it, and now want to delete it don't edit the name because that edits and updates the name of the query that you forked from - altering the description (code) is OK since that won't affect the original from which you forked. That probably is a bug @TimStone as it's unwanted behavior. – Rob Mar 14 at 2:31

You must log in to answer this question.

protected by Community Jun 20 '17 at 5:32

Thank you for your interest in this question. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).

Would you like to answer one of these unanswered questions instead?

Not the answer you're looking for? Browse other questions tagged .