Opened 8 years ago
Closed 7 years ago
#3317 closed defect (worksforme)
t.remove -rf does not unregister removed maps from temporal database
Reported by: | veroandreo | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | 7.2.3 |
Component: | Temporal | Version: | svn-trunk |
Keywords: | t.remove | Cc: | |
CPU: | x86-64 | Platform: | Linux |
Description
I used t.remove -rf inputs=bla1,bla2,bla3
to remove all strds and corresponding maps from a certain mapset I use for testing. However, I found that even though maps and strds were indeed removed (i.e.: they no longer appeared after t.list type=strds
or g.list type=raster
), maps were not unregistered from the temporal database. I only discovered this when I used t.list type=raster
. I had to remove those maps (i.e.: the corresponding entries for those maps in the temporal database) with G7:t.unregister.
I understand that maps are not unregistered from the temporal database when one only removes the strds, but if one removes both strds and maps (by means of -rf flags), wouldn't it be better to also unregister those maps from the temporal database by default? It seems confusing to also have to run t.unregister after having removed strds and maps.
Change History (3)
comment:1 by , 8 years ago
Milestone: | 7.2.1 → 7.2.2 |
---|
comment:2 by , 7 years ago
Milestone: | 7.2.2 → 7.2.3 |
---|
comment:3 by , 7 years ago
Resolution: | → worksforme |
---|---|
Status: | new → closed |
I'm closing as works for me, because I cannot reproduce this behavior any longer.
Ticket retargeted after milestone closed