On Fri, Apr 29, 2016 at 6:33 AM, <svn_grass@osgeo.org> wrote:
# v.db.select
v.db.select|nv:null_value
+v.db.select|fs:separator
v.db.select|vs:vertical_separator
Shouldn't the "global block" in renamed_options take care of nv and fs?
### Global
fs:separator
nv:null_value
dt:dtime
dp:precision
The command:
v.db.select bridges fs=comma
works for me in trunk in r68324 (i.e. before r68329) and gives expected
warning (Please update the usage of <v.db.select>: option <fs> has been
renamed to <separator>).
https://trac.osgeo.org/grass/browser/grass/trunk/lib/gis/renamed_options?rev=68329
https://trac.osgeo.org/grass/changeset/68329
On Fri, Apr 29, 2016 at 3:20 PM, Vaclav Petras <wenzeslaus@gmail.com> wrote:
On Fri, Apr 29, 2016 at 6:33 AM, <svn_grass@osgeo.org> wrote:
# v.db.select
v.db.select|nv:null_value
+v.db.select|fs:separator
v.db.select|vs:vertical_separator
Shouldn't the "global block" in renamed_options take care of nv and fs?
ah, I overlooked that!
https://trac.osgeo.org/grass/changeset/68329
Question: are modules automagically picked up for global block or do
they need to be listed?
If the former, shall I revert 68329?
Markus
On Fri, Apr 29, 2016 at 9:56 AM, Markus Neteler <neteler@osgeo.org> wrote:
> https://trac.osgeo.org/grass/changeset/68329
Question: are modules automagically picked up for global block or do
they need to be listed?
I don't see any list of modules to be considered for global and v.db.select
works with fs, so I would say global means "apply to all".
If the former, shall I revert 68329?
v.db.select bridges fs=comma works for me without r68329, so I would say
revert.
On Fri, Apr 29, 2016 at 4:12 PM, Vaclav Petras <wenzeslaus@gmail.com> wrote:
On Fri, Apr 29, 2016 at 9:56 AM, Markus Neteler <neteler@osgeo.org> wrote:
> https://trac.osgeo.org/grass/changeset/68329
...
so I would say revert.
Done.
Markus