[GRASS-dev] probable v.db.connect -g parsing problem

2009-08-24 Thread Hamish
Hi, I notice a probable problem parsing v.db.connect's -g output. An extra term containing the layer-name (if present) is added to the first data column. e.g. if layer 1 had the name layer_name G v.db.connect -g fields2 fs='|' 1/layer_name|fields2|cat|.../$MAPSET/dbf/|dbf instead of

Re: [GRASS-dev] probable v.db.connect -g parsing problem

2009-08-24 Thread Maris Nartiss
This is not an issue for gis.m in 6.5. Layer output of v.db.connect isn't used/parsed, as user's provided layer number is used. I was not able to find any (easy to spot) way how to name a layer, but IIRC there are some modules, that add a name to layer during it's creation. Maris. 2009/8/24,

Re: [GRASS-dev] probable v.db.connect -g parsing problem

2009-08-24 Thread Markus Metz
Hamish wrote: Hi, I notice a probable problem parsing v.db.connect's -g output. An extra term containing the layer-name (if present) is added to the first data column. e.g. if layer 1 had the name layer_name ... I am not an expert in these things so I ask: under what conditions would a