# Dropping dataset from code doesn't properly delete examples

**URL:** <https://support.prodi.gy/t/dropping-dataset-from-code-doesnt-properly-delete-examples/437>\
**Category:** Uncategorized\
**Tags:** done, database\
**Created:** [March 25, 2018, 4:48pm UTC](https://support.prodi.gy/t/dropping-dataset-from-code-doesnt-properly-delete-examples/437 "2018-03-25T16:48:01Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![geniki](https://avatars.discourse-cdn.com/v4/letter/g/ecb155/32.png) [@geniki](https://support.prodi.gy/u/geniki)\
**Post date:** [June 1, 2020, 9:47am UTC](https://support.prodi.gy/t/dropping-dataset-from-code-doesnt-properly-delete-examples/437/12 "2020-06-01T09:47:14Z")

</div>

Tried the above with no success.

Looking at the verbose Prodigy logs, it seems that named sessions create their additional separate "dataset" in the DB. `prodigy drop dataset1` doesn't delete `dataset1-user1` and that's what Prodigy picks up when I "re-create" the dataset. So to actually delete a dataset, I need to 1) look up all associated "datasets" and 2) manually drop them one by one. Is this the general and desired behaviour?

---

_[View the full topic](https://support.prodi.gy/t/dropping-dataset-from-code-doesnt-properly-delete-examples/437)._