Re: [GRASS-dev] v.db.update: any reason to keep both value and qcolumn parameter ?

2008-10-01 Thread Moritz Lennert
On 30/09/08 16:44, Glynn Clements wrote: Markus Neteler wrote: However, in its current version (since rev 23578), value is now adapted according to column type, which means that you cannot use column operations on varchar columns (e.g. concatenation). So, we should either: - change the doc to

Re: [GRASS-dev] v.db.update: any reason to keep both value and qcolumn parameter ?

2008-09-30 Thread Hamish
>>> However, in its current version (since rev 23578), value is now >>> adapted according to column type, which means that you cannot >>> use column operations on varchar columns (e.g. concatenation). this puts it at odds with the value= option description, both WRT quotes and combinations: "Valu

Re: [GRASS-dev] v.db.update: any reason to keep both value and qcolumn parameter ?

2008-09-30 Thread Michael Barton
voice: 480-965-6262; fax: 480-965-7671 www: http://www.public.asu.edu/~cmbarton On Sep 30, 2008, at 8:48 AM, <[EMAIL PROTECTED]> <[EMAIL PROTECTED] > wrote: Date: Tue, 30 Sep 2008 15:44:48 +0100 From: Glynn Clements <[EMAIL PROTECTED]> Subject: Re: [GRASS-dev] v.db.upd

Re: [GRASS-dev] v.db.update: any reason to keep both value and qcolumn parameter ?

2008-09-30 Thread Glynn Clements
Markus Neteler wrote: > > However, in its current version (since rev 23578), value is now adapted > > according to column type, which means that you cannot use column operations > > on varchar columns (e.g. concatenation). > > > > So, we should either: > > > > - change the doc to reflect that val

Re: [GRASS-dev] v.db.update: any reason to keep both value and qcolumn parameter ?

2008-09-30 Thread Markus Neteler
On Tue, Sep 30, 2008 at 10:58 AM, Moritz Lennert <[EMAIL PROTECTED]> wrote: > In v.db.update we currently have: > > #%option > #% key: value > #% type: string > #% description: Value to update the column with, can be (combination of) > other column(s) > #% required : no > #%end > #%option > #% key:

[GRASS-dev] v.db.update: any reason to keep both value and qcolumn parameter ?

2008-09-30 Thread Moritz Lennert
In v.db.update we currently have: #%option #% key: value #% type: string #% description: Value to update the column with, can be (combination of) other column(s) #% required : no #%end #%option #% key: qcolumn #% type: string #% description: Column to query #% required : no #%end 'qcolumn' wa