|
On 15/02/2013 01:42, Hamish wrote:
Markus Metz wrote:In GRASS 6.4.1- it was possible to have a separate sqlite db for each vector in $MAPSET/vector/$MAP/sqlite.db. I have no idea why this option has been disabled. The VAR file can beDB_DRIVER: sqlite DB_DATABASE: $GISDBASE/$LOCATION_NAME/$MAPSET/vector/$MAP/sqlite.db Should we revert the changes that make it now impossible to have a separate sqlite db for each vector?AFAIK it's still possible to have a separate sqlite db for each vector if you use v.db.connect (see v.pack.py), it's just that you can't tell db.connect to make that the default for all new maps. perhaps if [v.]db.connect understood to parse '$MAP' you could have a portable database='$GISDBASE/$LOCATION_NAME/$MAPSET/vector/$MAP/sqlite.db' string saved in the VAR file? (and so, by default but user- alterable, all sqlite layers for that map saved in the same file) "db.sqlite" or "sqlite.db" for the filename? If the $MAP variable is available, I'd like to see the database names as '$GISDBASE/$LOCATION_NAME/$MAPSET/vector/sqlite/$MAP.sqlite' and I think you're suggestion to put all layers for a vector into one sqlite file does make sense. THere are definitely situations where you want to join between different layers within the same vector. Having both in the same sqlite makes that easier. Hamish _______________________________________________ grass-user mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-user This mail was received via Mail-SeCure System. -- Micha Silver GIS Consulting 052-3665918 http://www.surfaces.co.il |
_______________________________________________ grass-user mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-user
