[GRASS-dev] nasty v.db.dropcolumn and v.db.join bug in GRASS7 + sqlite

Markus Metz markus.metz.giswork at googlemail.com
Thu Dec 22 06:58:02 EST 2011

On Mon, Dec 19, 2011 at 6:13 AM, Markus Neteler <neteler at osgeo.org> wrote:
> On Sun, Dec 18, 2011 at 12:07 PM, Markus Metz
> <markus.metz.giswork at googlemail.com> wrote:
>> On Wed, Nov 30, 2011 at 10:24 PM, Dylan Beaudette
>> <debeaudette at ucdavis.edu> wrote:
>>> Just noticed a nasty bug when using v.db.dropcolumn and v.db.join with a
>>> sqlite back-end. This seems to happen whenever a table is modified using the
>>> 'coltypes' as reported by the GRASS-DB API:
>> Please try trunk r49802.
>> The bug was in the sqlite driver who assumes a default column length
>> of 1 which is then adjusted according to the declared column type. A
>> declared column type CHARACTER without length info slipped through
>> with length = 1, although it is really a variable width TEXT field
>> which gets a dummy width of 1000 for clients which don't understand
>> variable-size fields.

> Great for catching this. If it helps, I vote for backporting to 6.4 to
> let it be in the upcoming 6.4.2 release.
Done in r49862.

Markus M

More information about the grass-dev mailing list