Parse-dashboard: Delete all rows in collection

[flessard]

Where is the delete all rows for a collection?

• [X] You're running version >=2.1.4 of Parse Server.
• [X] You've searched through existing issues. Chances are that your issue has been reported or resolved before.

[drew-gross]

dashboard.parse.com deletes all rows through a special endpoint on parse.com/apps, rather than api.parse.com. we decided that giving clients the ability to delete all object in a class was too likely to be abused, so we never implemented it. Parse Dashboard, though, only has methods in the JS sdk and methods on Parse Server available to it. Adding support for deleting all objects in a class would require a little bit of support on Parse Server, and a little bit of support from Parse Dashboard. It would be a good first PR for someone who wants to contribute to Parse.

[DazChong]

+1 I use mongo to drop collection.

[AmbroiseCollon]

+1 would be useful for testing

[miracle7]

+1

[hl4hck]

+1

[pie6k]

+1

[JustinDMoore]

+1

[pie6k]

Maybe at least some "Select all on screen" option on data browser?

Some websites have also such option that if I press mouse button on some checkbox and then (without releasing it) I move mouse to other checkboxes, they get selected too. That would save me a lot of clicking.

[samschooler]

Can someone explain why this checkbox in the header of collections is disabled?

I assume it would be for performance reasons? But If you inspect element, and enable it, it works and selects every element in the collection. It doesn't actually delete everything because it is probably a special case in code, but I could fix that to work as if every row was selected manually.

We could also just limited it to remove only 50 rows at a time to prevent overloading the server. Would this work?

[drew-gross]

We disabled it because it was confusing some people, and a few people accidentally deleted their entire collection. We were eventually going to change it so it selected only the visible rows, but we never got around to that.

[agordeev]

We disabled it because it was confusing some people, and a few people accidentally deleted their entire collection.

Well, I believe that disabled select all checkbox confuses people even more.

If few people accidentally deleted their entire collection, that's their problem. Do we have to find a workarounds because they are not smart enough to avoid pressing Delete button when all rows are selected?

[JustinDMoore]

Agree with @andrew8712 . Aren't they presented with a confirmation to delete, forcing them to type in the class name to confirm?

[grassland-curing-cfa]

Deployed the latest Parse-server 2.2.15 and Parse-dashboard 1.0.14.
When I ran "Delete all rows" from the Edit menu list, it gave me a "404 Not Found" error when it tried to run "DELETE clear", which was identified from my Firebug console.
Also, "Select all" was disabled.

[benpackard]

I don't see it mentioned here, but the 'Delete all rows' option also seems to do nothing. Is that also expected behavior? If so, should it be disabled in a similar fashion to the 'select all' checkbox?

Secondly, is deleting the mongoDB collection an appropriate alternative without additional side-effects?

[aksperiod]

+1

[drew-gross]

Should be fixed in 1.0.15 as long as you have the latest Parse Server.

[owldesign]

For people who still have disabled checkbox (old forks)..

Quick workaround would be to inspect the checkbox and remove disabled attribute, then you can use it to check all entries and remove them..