Hi, mw:Talk:Quarry is the place to ask Quarry questions or for Quarry help. Phabricator is mostly for feature requests or bug reports.

I think this is a fair enough request, since there's no way to actually do this right now in Quarry

Sure, this is much more feature request than a question

I'm not sure we should delete anything (short of doxing and the like). Maybe we can "archive" a draft so that it doesn't appear in your history of queries unless a "show archived queries" box is checked.

That's not so different from my current solution of renaming the unused queries to "~" and use them as a clean paper for new queries in the future.

I understand not deleting already published queries, but (in my opinion) drafts could be deleted without loosing any important content.

(I also do not fully understand publishing queries, if my not published drafts can see anybody logged in.)

Indeed, everything is public, and I think we're careful to not call them 'drafts' (if not we should be!)- published just means you are finished tweaking them for a bit.

Not sure what the right thing to do here is.

What I do — I just reuse the queries which better'd be deleted or which were just those empty ones. Once you've renamed and changed it nobody knows what it was before that. Perhaps some process for marking queries for reuse could be added (like a separate section where you can move queries to and from so that you can keep queries to be reused in there together, or any other way)

@Base The same as I do. That is a great idea to add a possibility to mark them for reuse.

btw: Maybe better would be draft vs done (instead of draft vs published) if everything is public

Yeah, I agree. I'm going to change the labels on it to avoid confusion.

The drafts can already be renamed, and their description and query can already be overwritten and resubmitted to effectively blank them permanently. As such, the ability to delete a draft wouldn't lose anything users can't already remove by hand, except for the url to return 404 instead of an empty draft.

But who wants to have a list full of empty drafts (like me)

BTW I use empty/emptied drafts to make "folders" (T164825: Add some type of folders/categories/sorting to user page)

Right. I think it makes a lot of sense to *archive* old queries so that they don't clutter up useful, but not-worth-publishing queries. Given that queries don't take up a huge amount of drive space, it seems the only reason for deleting them is to de-clutter one's activity history.

In T135908#4461580, @Halfak wrote:

Right. I think it makes a lot of sense to *archive* old queries so that they don't clutter up useful, but not-worth-publishing queries. Given that queries don't take up a huge amount of drive space, it seems the only reason for deleting them is to de-clutter one's activity history.

Any solution to these two problems (possibility to hide unused and possibility to reorganize used in some fashion) would be great

My 2cents: I created a new query by mistake, it is a draft and the fact that I cannot delete it is super annoying. I am ok with the idea of not deleting published queries.

When you click publish you know that they are going to be out there forever, just like Wikipedia revisions, but drafts should be "like tears in the rain".

If you ask me, published queries should be there or archived (to mark that a given query maybe is not maintained anymore or obsolete), and you should be able to delete drafts.

FWIW, I think there's a big difference between "delete" and "archive". Delete breaks links and hides past activity. Archive gets stuff I don't want to see out of the way. I think "archive" is the right metaphor here. I would hate it if someone could no longer download the results of a query because some user decided to delete it.

That said, if a query was never executed, maybe it should be delete-able forever. It's hard to imagine any secondary effects of deleting a query that was never run.

As I understand it, past versions of draft queries (not published queries) are not kept. So the dozen drafts I have at https://quarry.wmflabs.org/Krinkle have (by my choosing) already been broken for all intents and purposes.

I now keep them there and try to remember to repurpose of them the empty/unnamed drafts for my next real query so that I eventually run out of them, however this rarely works in practice as for every three throw-away queries I run I tend to remember once and forget twice, thus building up ever more untitled/empty drafts.

In T135908#6827926, @Krinkle wrote:

As I understand it, past versions of draft queries (not published queries) are not kept. So the dozen drafts I have at https://quarry.wmflabs.org/Krinkle have (by my choosing) already been broken for all intents and purposes.

They are kept, you can click the history button to see the previous versions of the query and their results.

I would really like a way to delete old queries. Publicly publishing every single query I ever make with no way to remove them is creepy behaviour. It's also not made clear to people that (unlike other queries, like on-wiki searches, API queries or SPARQL queries), any query they run in Quarry will be publicly visible and attributed to them forever, even if they don't publish it (as can be seen by the comments above).

In T135908#8718121, @Nikki wrote:

In T135908#6827926, @Krinkle wrote:

As I understand it, past versions of draft queries (not published queries) are not kept. So the dozen drafts I have at https://quarry.wmflabs.org/Krinkle have (by my choosing) already been broken for all intents and purposes.

They are kept, you can click the history button to see the previous versions of the query and their results.

You are correct, though at the time of writing this was not the case, previous queries could not be seen, that was introduced in T100982

I would really like a way to delete old queries. Publicly publishing every single query I ever make with no way to remove them is creepy behaviour. It's also not made clear to people that (unlike other queries, like on-wiki searches, API queries or SPARQL queries), any query they run in Quarry will be publicly visible and attributed to them forever, even if they don't publish it (as can be seen by the comments above).

I don't disagree. Even as the person who introduced the patch that exposed the history. In further reflection it seems like a strange feature. Though there is renewed focus in replacing Quarry with something better in T169452 which may solve all the things.