#513: g.rename extremely slow, speed improvement
--------------------------+------------------------------------
Reporter: gisboa | Owner: grass-dev@…
Type: enhancement | Status: new
Priority: minor | Milestone: 6.4.0
Component: Vector | Version: unspecified
Resolution: | Keywords: vector database rename
CPU: All | Platform: All
--------------------------+------------------------------------
Comment (by glynn):
Replying to [comment:1 glynn]:
> Suggestion 1: drop support for the DBF driver. Its presence means that
everything that uses the DBMI has to limit itself to the tiny subset of
SQL which the DBF driver actually understands (e.g.: no joins), often
having to adopt inefficient workarounds.
+1
> Suggestion 3: upgrade the DBF driver so that it supports at least the
basic features of SQL, e.g. joins.
This is far from straightforward. You'd need to write a query optimiser,
and you'd need to maintain indices. Ultimately, efficient implementation
of joins is the heart of any RDBMS.
Extending it to support isolated features such as renaming tables or
columns probably wouldn't be particularly hard, although it's debatable
whether there's any point given that the lack of support for joins makes
it inferior to SQLite in every regard.
--
Ticket URL: <https://trac.osgeo.org/grass/ticket/513#comment:3>
GRASS GIS <https://grass.osgeo.org>