Hi Mira,
AFAICT, yes. See here:
https://github.com/OSGeo/grass/commit/1be7bfe59f1c71b12fe60a26a3aa313b9a599e31
However, the fix will only come with the new release, 7.8.4. In the
meantime, you can download the source code and compile release branch to
get this bugfix. See here:
Sorry to open this again:
Was the change really backported to GRASS 7.8? I still cannot set an
overwrite flag in the gui.
I use 7.8.3-1~bionic1
on linux mint 19
from http://ppa.launchpad.net/ubuntugis/ubuntugis-unstable/ubuntu
bionic/main amd64
Is that the wrong source?
Thanks,
Mira
On Thu, Jul 16, 2020 at 12:34 PM Helmut Kudrnovsky wrote:
> Mira Kattwinkel wrote
> > Dear list,
> >
> > in GRASS 7.8 v.to.db creates a new column in contrast to previous
> > versions where it column had to exist before.
...
>
>
> yes there was a change in the module behaviour, see
>
>
Mira Kattwinkel wrote
> Dear list,
>
>
> in GRASS 7.8 v.to.db creates a new column in contrast to previous
> versions where it column had to exist before.
>
> According to the manual "If the /column/ exists, the *--overwrite* flag
> is required to overwrite it". However, this flag does not
Dear list,
in GRASS 7.8 v.to.db creates a new column in contrast to previous
versions where it column had to exist before.
According to the manual "If the /column/ exists, the *--overwrite* flag
is required to overwrite it". However, this flag does not exist. Hence,
if the column is
