[GRASS-dev] nasty v.db.dropcolumn and v.db.join bug in GRASS7 +
debeaudette at ucdavis.edu
Tue Dec 20 12:09:34 EST 2011
On Sunday, December 18, 2011, Markus Neteler 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
> >> '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.
Thanks for making those fixes, much appreciated!
Dylan E. Beaudette
USDA-NRCS Soil Scientist
California Soil Resource Lab
More information about the grass-dev