[GRASS-dev] [GRASS GIS] #1863: DBMI Protocol Error in v.extract

#1863: DBMI Protocol Error in v.extract
-------------------------+--------------------------------------------------
Reporter: dkavanagh | Owner: grass-dev@…
     Type: defect | Status: new
Priority: normal | Milestone: 7.0.0
Component: Vector | Version: svn-trunk
Keywords: | Platform: MSWindows 7
      Cpu: Unspecified |
-------------------------+--------------------------------------------------
I am getting a DBMI Protocol error in v.extract when I query a field value
that is equal to 10 (e.g. HCA_ID=10). The exact command is:

v.extract -t --overwrite input=cores type=area where=HCA_ID=10 output=core

If I filter for 9, 11, 20 or 100 the problem does not occur.

I opened the sqlite database directly and queried it. No errors occurred.
The field type is integer.

I originally encountered the problem when I ran the v.extract command in a
Python script. The script hangs and does not report an error. You have to
kill the sqlite exe to free the file lock.

--
Ticket URL: <http://trac.osgeo.org/grass/ticket/1863&gt;
GRASS GIS <http://grass.osgeo.org>

#1863: DBMI Protocol Error in v.extract
-----------------------+----------------------------------------------------
Reporter: dkavanagh | Owner: grass-dev@…
     Type: defect | Status: new
Priority: normal | Milestone: 7.0.0
Component: Vector | Version: svn-trunk
Keywords: | Platform: MSWindows 7
      Cpu: x86-64 |
-----------------------+----------------------------------------------------
Changes (by dkavanagh):

* cc: dkavanagh (added)
  * cpu: Unspecified => x86-64

--
Ticket URL: <http://trac.osgeo.org/grass/ticket/1863#comment:1&gt;
GRASS GIS <http://grass.osgeo.org>

#1863: DBMI Protocol Error in v.extract
-----------------------------------+----------------------------------------
Reporter: dkavanagh | Owner: grass-dev@…
     Type: defect | Status: new
Priority: normal | Milestone: 7.0.0
Component: Vector | Version: svn-trunk
Keywords: sqlite dbmi v.extract | Platform: MSWindows 7
      Cpu: x86-64 |
-----------------------------------+----------------------------------------
Changes (by dkavanagh):

  * keywords: => sqlite dbmi v.extract

--
Ticket URL: <http://trac.osgeo.org/grass/ticket/1863#comment:2&gt;
GRASS GIS <http://grass.osgeo.org>

#1863: DBMI Protocol Error in v.extract
-------------------------------------+--------------------------------------
Reporter: dkavanagh | Owner: grass-dev@…
     Type: defect | Status: new
Priority: normal | Milestone: 7.0.0
Component: Vector | Version: svn-trunk
Keywords: sqlite, dbmi, v.extract | Platform: MSWindows 7
      Cpu: x86-64 |
-------------------------------------+--------------------------------------
Changes (by neteler):

  * keywords: sqlite dbmi v.extract => sqlite, dbmi, v.extract

Comment:

Replying to [ticket:1863 dkavanagh]:
> I am getting a DBMI Protocol error in v.extract

Please post also the error here.

And, do you use a recent GRASS 7 snapshot?

--
Ticket URL: <http://trac.osgeo.org/grass/ticket/1863#comment:3&gt;
GRASS GIS <http://grass.osgeo.org>

#1863: DBMI Protocol Error in v.extract
-------------------------------------+--------------------------------------
Reporter: dkavanagh | Owner: grass-dev@…
     Type: defect | Status: new
Priority: normal | Milestone: 7.0.0
Component: Vector | Version: svn-trunk
Keywords: sqlite, dbmi, v.extract | Platform: MSWindows 7
      Cpu: x86-64 |
-------------------------------------+--------------------------------------

Comment(by dkavanagh):

On further testing the problem is not due to the number 10 but its row
position, i.e. '''row 10'''. A colleague, working with a different input,
encounters the same issue once row 10 is queried. We can select above and
below but not row 10 itself.

The data is imported from a shape file using v.in.ogr. Strangely, I cannot
use the same name when importing, it just hangs. Instead of using -
''v.in.ogr dsn=cores.shp output=cores''
I have to use -
''v.in.ogr dsn=cores.shp output=gcores''

The error is -
dbmi: Protocol error
ERROR: Unable select records from table <gcores>
The error is not reported when it is called within a python script.

I just tested today with the most recent build
(WinGRASS-7.0.svn-r54762-480-Setup). The problem still exists. It did not
occur in a build from May of last year
(WinGRASS-7.0.svn-r51660-239-Setup.exe).

--
Ticket URL: <http://trac.osgeo.org/grass/ticket/1863#comment:4&gt;
GRASS GIS <http://grass.osgeo.org>