[GRASS5] connecting a table to a view in pg driver

GRASS GIS GRASS GIS developer
1

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

Is it possible to connect a map to a view in postgres ? I get :

v.db.connect -o bxlgdsec table=vespvie

WARNING: Table <vespvie> does not exist in database <grass>
WARNING: The table <vespvie> is now part of vector map <bxlgdsec>
and may be deleted or overwritten by GRASS modules.

Does this mean it is not possible, or that I am doing something wrong ?

Moritz

P.S. Is it a bug or a feature that v.db.connect registers the
connection to a nonexisting table ? Shouldn't it fail and leave the
settings as before the command ?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDKFyurIrMbm76jD8RArcnAJ0W9mNEefyFgIagZd7tIh5MHO4XIQCfUCcY
Rr6b5C/3A8SacTMjYePp4vQ=
=PwL7
-----END PGP SIGNATURE-----

2

On 9/14/05, Moritz Lennert <mlennert@club.worldonline.be> wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

Is it possible to connect a map to a view in postgres ? I get :

> v.db.connect -o bxlgdsec table=vespvie
WARNING: Table <vespvie> does not exist in database <grass>
WARNING: The table <vespvie> is now part of vector map <bxlgdsec>
and may be deleted or overwritten by GRASS modules.

Does this mean it is not possible, or that I am doing something wrong ?

It is only warning, the connection is created.

Moritz

P.S. Is it a bug or a feature that v.db.connect registers the
connection to a nonexisting table ? Shouldn't it fail and leave the
settings as before the command ?

No, it is feature, GRASS always does what you want, only if
it seems to be strange, it prints a warning. Thanks to this feature
you can work with view.

The bug is, that it does not check also available views.

Radim