I’m sometimes to find a way to delete a database via database itself or site structure, but it seems there’s no option with it. Could you add an option to delete database, if I want to free up the clutter? Sometimes I don’t want to use my database anymore and create new database. Also apply the same with live data.
48 Likes
I’M agree and rename also!
that’s true
1.delete database
2.Rename Database
Me too, delete would be best but failing that at least the ability to rename so the database can be re-purposed
I agree.
1.delete database
2.Rename Database
I dont even understand why this option is not added by now. It’s quite important in my opinion and i see absolutly no reason to not have the feature to delete/rename collections. As you can simply export to csv to keep old data, then reupload into a new collection (with other fields eg) if necessary. Please add this
I agree as well. Please add this feature. It is not simply desired it is pretty much a requirement.
I agree as well. We need to delete some database and remane her. I vote for this evolution
PLEASE ADD THIS
I agree. This really should be in. After creating a functional set of databases, I later thought of an easier way to manage them, yet found myself unable to due to the lack of features. Please add this in. I understand that you are in BETA but this stuff should really be included as standard…
Please add
Hey!
Yeah, that’s really annoying that you can’t delete collection, so this feature will definitely be available some time in the future, but let’s ignore specific timeline for now.
Meanwhile, what would be your expectations from such a functionality?
- Would it be even more annoying if you could permanently delete Collection, and not revert this action? Or, is it a must to have a Trash (soft delete), but then not be able to create the collection with the same name until the permanent deletion (hard delete)?
- What would you expect to happen with your Dynamic Page, Datasets, code, and reference fields in another collections when you delete collection?
Would really appreciate your thoughts!
- I think as long as you had clear confirmation that this was final and you will lose all data, then it is user beware. (Maybe have option to export first?)
- Would default to not being linked.
- Agree with Splatty
- Same way you get prompted when changing a field’s type. “All connections will be lost”
HI ADAS, Here’s what I think about Delete
2-If collection is already connected and in use somewhere in the WEBsite don’t allow to Delete it (display active collections page list to notice user where this Dataset is in use), it will force WEB owner to Delete active Database (Dataset) in all web pages before allowing to delete it. If this collection is not Use, Your suggestion 1 soft delete is good for me!
a must have
This should have been an obvious requirement. “This is a beta” is not an excuse for such a basic feature to not be included. Perhaps deleting would be a little more difficult, but renaming is about as simple as it gets.
Yes please. Tried making a test database to try this thing out, made a field mistake, now I can’t fix it. Sense a lot of mishaps moving forward if I want to learn this thing…
Thanks for your response Adas. I like the trash option. Also an automatic re-naming of the collection after we delete it would be nice. Like, for example “mycollection-deleted-dateofdeletion”. I could recover the collection and still know I deleted it previously. I could also re-name it after I recovered it. This would allow me to also create a fresh new collection with the same name without worrying about having to come up with something new. As for warning us when it is still connection to our website, let us know what pages it is connected to. Otherwise, I still want the ability to override the connection and delete the database because I might know where it’s connected already. Just a time saver.
Thanks everyone for your input! You have great suggestions here.