Dropdown menu query_column in v.to.db shows columns of wrong table

[pvanbosgeo]

Concerns: The query_column option in the Query tab of the v.to.db function

Issue: when selecting layer 2 in the query_layer option, the dropdown menu of the query_column still shows the column name of the attribute table linked to layer 1 instead of the table linked to layer 2.

Warning: if one selects a column (e.g., VAR1) from the drop-down menu and runs v.to.db, a error is raised that "ERROR: Cannot open cursor: 'SELECT VAR1 FROM MYTAB WHERE cat = 15'"

Note: One can still type in the name of the required column, and the function will run without problem.

I am running GRASS 7.3 on Ubuntu 16.04

[pvanbosgeo]

Even though layer 2 is selected, the dropdown menu shows the column names of the table linked to layer 1

[mlennert]

Replying to pvanbosgeo:

Concerns: The query_column option in the Query tab of the v.to.db function

Issue: when selecting layer 2 in the query_layer option, the dropdown menu of the query_column still shows the column name of the attribute table linked to layer 1 instead of the table linked to layer 2.

AFAIK, this is an issue in every single module where a list of columns comes from another source than the main 'map'. AFAIU, this is inherent to the way this widget is programmed in the GUI. ISTR that there have been discussions about this, but don't have the time to search for this. I would guess that the widget would need some parameter with the name and layer of the map from which to get the list of column...

[martinl]

Unable to reproduce bug in GRASS 7.6.0