Open RichardPilbery opened 7 years ago
also using 0.2-8. But very new to this.
I've also found this problem. I have been creating an interview transcript file but if I find an error I like to correct that original file, then I want to re-import it using that same filename.
As I read through documentation it seems that the philosophy is not to actually delete any entry in the database but it gets reset in the 'status' column from 1 to 0 or even -1. So far I've come up with two workarounds, but I'd prefer to be able to do the full delete. Method 1: one workaround is to go in using FireFox and delete it in there from the list of files (sources).
Method 2: A slightly better workaround, still not that nice but preserves some of the integrity, is first to rename the file to something you don't want to use, THEN delete it so it doesn't appear in your list. then I think you'll be able to re-import.
Maybe someone can tell us both how it is meant to be done! :-)
Having the same problem. Not sure how to edit the database. Tried using DB Browser for SQlite on the project file but it did not show any data.
Hi nilz,
I am DELETING this post as really the better solution is below - using pdelete and CleanProject
Hope that is helpful. All I have time for right now. RQDA has been useful to me - I've needed to write up a couple of other procedures to make things work better, but so far helpful.
Chris
Hi Nils, Better solution just found! (Maybe it was there all the time but I can't be sure).
Look up how to use pdelete and CleanProject. See this documentation ...
https://www.rdocumentation.org/packages/RQDA/versions/0.3-0/topics/Deletion
Although it looks like it is more trouble to delete objects but this allows you to also Undelete if you make a mistake. So this is a better solution! Thanks to Ronggui.
Chris
@Chris-JAC I'm glad I bumped into this! Was wondering about this issue.
Using 0.2-8. If you import a file (CSV in my case), delete it and then try to re-import it, an error: 'A file with the same name exists in the database' appears. It looks like the entry is not being deleted from the source table when it is removed.