[GRASS-user] batch file processiong stops with some db-commands
Markus Neteler
neteler at osgeo.org
Wed Apr 13 16:44:30 EDT 2011
On Mon, Mar 14, 2011 at 10:36 PM, Markus Neteler <neteler at osgeo.org> wrote:
> On Sat, Mar 12, 2011 at 5:48 PM, Matthias Klingel
> <matthias.klingel at web.de> wrote:
>>
>> Dear grass users,
>> in wingrass 6.4.1 (or at least on my machine), processing of batch files with grass commands stops after executing v.db.addtable, v.db.addcol, v.db.addcol, v.db.dropcol and their db.* equivalents. The rest of the batch file will not be processed. Of course, there is a workaround using SQL commands with db.execute, but this is substantially more typing work. Anybody has the same problem and knows how to fix it?
>
> Do you use the DBF driver? Perhaps you are hit by this bug:
> http://trac.osgeo.org/grass/ticket/1308
>
> Hopefully solved soon...
For the record:
solved in GRASS 6.4.1 which has been published now.
Markus
More information about the grass-user
mailing list