I want to use ‘r.to.vect’ but it seems to default to a ‘Postgis’ table that has no geometry column just a table with a ‘cat’ id. I would like to export to ‘sqlite’. I have both postgres an sqlite login details stored in ‘db.login’. How do i switch between the two or at least make sqlite the default? If I change settings with ‘db.connect’ to ‘sqlite’ it fails (error below) but still keeps holding onto the ‘grass_gis’ schema form the Postgis connection!
r.to.vect input=APGB_aerial_2_i_segment_drained_peat_with_exposed_haggs@PERMANENT output=test1 type=area
DBMI-SQLite driver error:
Error in sqlite3_prepare():
unknown database grass_gis
DBMI-SQLite driver error:
Error in sqlite3_prepare():
unknown database grass_gis
ERROR: Unable to create table: create table grass_gis.test1 ( cat integer, value integer, label varchar(10))
WARNING: Table <grass_gis.test1> linked to vector map does not exist
Is there a preferred option to change databases more cleanly.
I want to use ‘r.to.vect’ but it seems to default to a ‘Postgis’ table that has no geometry column just a table with a ‘cat’ id. I would like to export to ‘sqlite’. I have both postgres an sqlite login details stored in ‘db.login’. How do i switch between the two or at least make sqlite the default? If I change settings with ‘db.connect’ to ‘sqlite’
what is the exact command you used to set the default connection to sqlite?
You can also try db.connect -d, otherwise you might need to specify the default database to be used.
In any case, please verify first with db.connect -p to see the connection details used when creating a new vector.
Markus M
it fails (error below) but still keeps holding onto the ‘grass_gis’ schema form the Postgis connection!
r.to.vect input=APGB_aerial_2_i_segment_drained_peat_with_exposed_haggs@PERMANENT output=test1 type=area
DBMI-SQLite driver error:
Error in sqlite3_prepare():
unknown database grass_gis
DBMI-SQLite driver error:
Error in sqlite3_prepare():
unknown database grass_gis
ERROR: Unable to create table: create table grass_gis.test1 ( cat integer, value integer, label varchar(10))
WARNING: Table <grass_gis.test1> linked to vector map does not exist
Is there a preferred option to change databases more cleanly.
Default driver / database set to:
driver: sqlite
database: C:\TempLocation\PERMANENT\sqlite\sqlite.db
(Mon Jul 02 14:19:40 2018) Command finished (0 sec)
Still holding ‘schema’ and ‘group’ details from PostGIS. Shouldn’t these have been dropped when changing to sqlite which is perhaps why the connection is failing?
I want to use ‘r.to.vect’ but it seems to default to a ‘Postgis’ table that has no geometry column just a table with a ‘cat’ id. I would like to export to ‘sqlite’. I have both postgres an sqlite login details stored in ‘db.login’. How do i switch between the two or at least make sqlite the default? If I change settings with ‘db.connect’ to ‘sqlite’
what is the exact command you used to set the default connection to sqlite?
You can also try db.connect -d, otherwise you might need to specify the default database to be used.
In any case, please verify first with db.connect -p to see the connection details used when creating a new vector.
Markus M
it fails (error below) but still keeps holding onto the ‘grass_gis’ schema form the Postgis connection!
r.to.vect input=APGB_aerial_2_i_segment_drained_peat_with_exposed_haggs@PERMANENT output=test1 type=area
DBMI-SQLite driver error:
Error in sqlite3_prepare():
unknown database grass_gis
DBMI-SQLite driver error:
Error in sqlite3_prepare():
unknown database grass_gis
ERROR: Unable to create table: create table grass_gis.test1 ( cat integer, value integer, label varchar(10))
WARNING: Table <grass_gis.test1> linked to vector map does not exist
Is there a preferred option to change databases more cleanly.
Still holding ‘schema’ and ‘group’ details from PostGIS. Shouldn’t these have been dropped when changing to sqlite which is perhaps why the connection is failing?
yes.
It seems that db.connect -g is better than db.connect -p to verify connection settings, e.g. I get in the North Carolina sample dataset
I want to use ‘r.to.vect’ but it seems to default to a ‘Postgis’ table that has no geometry column just a table with a ‘cat’ id. I would like to export to ‘sqlite’. I have both postgres an sqlite login details stored in ‘db.login’. How do i switch between the two or at least make sqlite the default? If I change settings with ‘db.connect’ to ‘sqlite’
what is the exact command you used to set the default connection to sqlite?
You can also try db.connect -d, otherwise you might need to specify the default database to be used.
In any case, please verify first with db.connect -p to see the connection details used when creating a new vector.
Markus M
it fails (error below) but still keeps holding onto the ‘grass_gis’ schema form the Postgis connection!
r.to.vect input=APGB_aerial_2_i_segment_drained_peat_with_exposed_haggs@PERMANENT output=test1 type=area
DBMI-SQLite driver error:
Error in sqlite3_prepare():
unknown database grass_gis
DBMI-SQLite driver error:
Error in sqlite3_prepare():
unknown database grass_gis
ERROR: Unable to create table: create table grass_gis.test1 ( cat integer, value integer, label varchar(10))
WARNING: Table <grass_gis.test1> linked to vector map does not exist
Is there a preferred option to change databases more cleanly.
Still holding ‘schema’ and ‘group’ details from PostGIS. Shouldn’t these have been dropped when changing to sqlite which is perhaps why the connection is failing?
yes.
It seems that db.connect -g is better than db.connect -p to verify connection settings, e.g. I get in the North Carolina sample dataset
I want to use ‘r.to.vect’ but it seems to default to a ‘Postgis’ table that has no geometry column just a table with a ‘cat’ id. I would like to export to ‘sqlite’. I have both postgres an sqlite login details stored in ‘db.login’. How do i switch between the two or at least make sqlite the default? If I change settings with ‘db.connect’ to ‘sqlite’
what is the exact command you used to set the default connection to sqlite?
You can also try db.connect -d, otherwise you might need to specify the default database to be used.
In any case, please verify first with db.connect -p to see the connection details used when creating a new vector.
Markus M
it fails (error below) but still keeps holding onto the ‘grass_gis’ schema form the Postgis connection!
r.to.vect input=APGB_aerial_2_i_segment_drained_peat_with_exposed_haggs@PERMANENT output=test1 type=area
DBMI-SQLite driver error:
Error in sqlite3_prepare():
unknown database grass_gis
DBMI-SQLite driver error:
Error in sqlite3_prepare():
unknown database grass_gis
ERROR: Unable to create table: create table grass_gis.test1 ( cat integer, value integer, label varchar(10))
WARNING: Table <grass_gis.test1> linked to vector map does not exist
Is there a preferred option to change databases more cleanly.
Still holding ‘schema’ and ‘group’ details from PostGIS. Shouldn’t these have been dropped when changing to sqlite which is perhaps why the connection is failing?
yes.
It seems that db.connect -g is better than db.connect -p to verify connection settings, e.g. I get in the North Carolina sample dataset
I want to use ‘r.to.vect’ but it seems to default to a ‘Postgis’ table that has no geometry column just a table with a ‘cat’ id. I would like to export to ‘sqlite’. I have both postgres an sqlite login details stored in ‘db.login’. How do i switch between the two or at least make sqlite the default? If I change settings with ‘db.connect’ to ‘sqlite’
what is the exact command you used to set the default connection to sqlite?
You can also try db.connect -d, otherwise you might need to specify the default database to be used.
In any case, please verify first with db.connect -p to see the connection details used when creating a new vector.
Markus M
it fails (error below) but still keeps holding onto the ‘grass_gis’ schema form the Postgis connection!
r.to.vect input=APGB_aerial_2_i_segment_drained_peat_with_exposed_haggs@PERMANENT output=test1 type=area
DBMI-SQLite driver error:
Error in sqlite3_prepare():
unknown database grass_gis
DBMI-SQLite driver error:
Error in sqlite3_prepare():
unknown database grass_gis
ERROR: Unable to create table: create table grass_gis.test1 ( cat integer, value integer, label varchar(10))
WARNING: Table <grass_gis.test1> linked to vector map does not exist
Is there a preferred option to change databases more cleanly.
Le Mon, 2 Jul 2018 16:36:30 +0200,
Markus Metz <markus.metz.giswork@gmail.com> a écrit :
On Mon, Jul 2, 2018 at 4:04 PM, Paul Shapley <p.shapley@gmail.com>
wrote:
>
> Hi Markus,
>
> Used 'db.connect' driver=sqlite
database=$GISDBASE/$LOCATION_NAME/$MAPSET/sqlite/sqlite.db
>
> I had to delete 'database schema=grass_gis'
>
> I had to delete 'default group=postgis_reader'
That seems to be a bug in db.connect, apparently it is not possible to
reset schema and group. Can you please open a ticket?
AFAIR, schema= and group= (i.e. without any value) should reset these
parameters.
Still holding ‘schema’ and ‘group’ details from PostGIS. Shouldn’t these have been dropped when changing to sqlite which is perhaps why the connection is failing?
yes.
It seems that db.connect -g is better than db.connect -p to verify connection settings, e.g. I get in the North Carolina sample dataset
I want to use ‘r.to.vect’ but it seems to default to a ‘Postgis’ table that has no geometry column just a table with a ‘cat’ id. I would like to export to ‘sqlite’. I have both postgres an sqlite login details stored in ‘db.login’. How do i switch between the two or at least make sqlite the default? If I change settings with ‘db.connect’ to ‘sqlite’
what is the exact command you used to set the default connection to sqlite?
You can also try db.connect -d, otherwise you might need to specify the default database to be used.
In any case, please verify first with db.connect -p to see the connection details used when creating a new vector.
Markus M
it fails (error below) but still keeps holding onto the ‘grass_gis’ schema form the Postgis connection!
r.to.vect input=APGB_aerial_2_i_segment_drained_peat_with_exposed_haggs@PERMANENT output=test1 type=area
DBMI-SQLite driver error:
Error in sqlite3_prepare():
unknown database grass_gis
DBMI-SQLite driver error:
Error in sqlite3_prepare():
unknown database grass_gis
ERROR: Unable to create table: create table grass_gis.test1 ( cat integer, value integer, label varchar(10))
WARNING: Table <grass_gis.test1> linked to vector map does not exist
Is there a preferred option to change databases more cleanly.
Am 2. Juli 2018 21:06:15 MESZ schrieb Markus Metz <markus.metz.giswork@gmail.com>:
On Mon, Jul 2, 2018 at 4:54 PM, Moritz Lennert
<mlennert@club.worldonline.be>
wrote:
Le Mon, 2 Jul 2018 16:36:30 +0200,
Markus Metz <markus.metz.giswork@gmail.com> a écrit :
> On Mon, Jul 2, 2018 at 4:04 PM, Paul Shapley <p.shapley@gmail.com>
> wrote:
> >
> > Hi Markus,
> >
> > Used 'db.connect' driver=sqlite
> database=$GISDBASE/$LOCATION_NAME/$MAPSET/sqlite/sqlite.db
> >
> > I had to delete 'database schema=grass_gis'
> >
> > I had to delete 'default group=postgis_reader'
>
> That seems to be a bug in db.connect, apparently it is not possible
to
> reset schema and group. Can you please open a ticket?
AFAIR, schema= and group= (i.e. without any value) should reset these
parameters.
That means no answer to schema and group would be a reasonable default
answer in order to easily change the current connection parameters?
No, should was the wrong word: does would have been better. AFAIR, explicitly setting them to no answer already did reset them.