[GRASS-dev] v.in.db: even with "where=" option the entire table is copied

GRASS GIS GRASS GIS developer
1

Hi,

I have found a nice bug in v.in.db:
Even when I use a "where=" SQL statement to limit the
number of points fetched from the DB, the entire table
is copied. The module uses db_copy_table() which isn't
appropriate.

v.extract builds a list of cats to copy, then uses
db_copy_table_by_ints(). So far I failed to transfer
this approach to v.in.db.

Help appreciated...
thanks
Markus

2

Hi,

2006/11/29, Markus Neteler <neteler@itc.it>:

I have found a nice bug in v.in.db:
Even when I use a "where=" SQL statement to limit the
number of points fetched from the DB, the entire table
is copied. The module uses db_copy_table() which isn't
appropriate.

v.extract builds a list of cats to copy, then uses
db_copy_table_by_ints(). So far I failed to transfer
this approach to v.in.db.

fixed in CVS and backported to 6.2

Martin

Help appreciated...
thanks
Markus

_______________________________________________
grass-dev mailing list
grass-dev@grass.itc.it
http://grass.itc.it/mailman/listinfo/grass-dev

--
Martin Landa <landa.martin@gmail.com> * http://gama.fsv.cvut.cz/~landa *