Opened 10 years ago
Last modified 6 years ago
#2569 new enhancement
Allow v.db.reconnect.all to handle database errors more graciously
| Reported by: | ewcgrass | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | 7.6.2 |
| Component: | Database | Version: | unspecified |
| Keywords: | Cc: | ||
| CPU: | x86-64 | Platform: | Linux |
Description
v.db.reconnect.all appears to stop at every database error it encounters during migration of database tables from .dbf to sqlite (and likely others too). While this provides a great opportunity to clean up incorrect database tables, it destroys work flow.
It would be nice if flags could be added to allow v.db.reconnect.all to skip errors and list them, while continuing to process the rest of the database tables in the mapset. Then those tables which caused the errors could be more easily audited and repaired.
This would be extremely useful for the numerous vector file migrations that are necessary from GRASS 6.x to 7.0, but it may be too late to incorporate it into version 7.0 at this time, which is why I suggest it as something for version 7.1 or later.
Change History (9)
comment:1 by , 9 years ago
| Milestone: | 7.1.0 → 7.2.0 |
|---|
comment:3 by , 8 years ago
| Milestone: | 7.2.1 → 7.2.2 |
|---|
comment:4 by , 7 years ago
| Milestone: | 7.2.2 → 7.4.0 |
|---|
All enhancement tickets should be assigned to 7.4 milestone.
comment:6 by , 7 years ago
| Milestone: | 7.4.1 → 7.4.2 |
|---|
comment:7 by , 6 years ago
| Milestone: | 7.4.2 → 7.6.0 |
|---|
All enhancement tickets should be assigned to 7.6 milestone.
Milestone renamed