Hi devs,
I have problem to open the temporal database (with grass70svn and grass71)
t.list
ERROR: Unable to connect to sqlite3 database:
/grassdata/latlong/ecad100_climate/tgis/sqlite.db
Exception: "unable to open database file"
Please use t.connect to set a read- and writable temporal database backend
permissions on the file seems to be correct,
ls -lh /grassdata/latlong/ecad100_climate/tgis/
totale 49M
-rw-r--r-- 1 lucadelu gis 49M set 3 2014 sqlite.db
Were there any changes in the temporal code that doesn't recognize the
old database structure?
--
ciao
Luca
http://gis.cri.fmach.it/delucchi/
www.lucadelu.org
Hi Luca,
i did not change the database structure of the temporal framework recently.
The exception seems to be from the sqlite3 backend, hence it should
not be related to different temporal database formats.
Can you access the database with the sqlite3 command directly?
sqlite3 /grassdata/latlong/ecad100_climate/tgis/sqlite.db
Best regards
Soeren
2015-06-11 15:14 GMT+02:00 Luca Delucchi <lucadeluge@gmail.com>:
Hi devs,
I have problem to open the temporal database (with grass70svn and grass71)
t.list
ERROR: Unable to connect to sqlite3 database:
/grassdata/latlong/ecad100_climate/tgis/sqlite.db
Exception: "unable to open database file"
Please use t.connect to set a read- and writable temporal database backend
permissions on the file seems to be correct,
ls -lh /grassdata/latlong/ecad100_climate/tgis/
totale 49M
-rw-r--r-- 1 lucadelu gis 49M set 3 2014 sqlite.db
Were there any changes in the temporal code that doesn't recognize the
old database structure?
--
ciao
Luca
http://gis.cri.fmach.it/delucchi/
www.lucadelu.org
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
On 11 June 2015 at 21:54, Sören Gebbert <soerengebbert@googlemail.com> wrote:
Hi Luca,
Hi Soeren,
i did not change the database structure of the temporal framework recently.
The exception seems to be from the sqlite3 backend, hence it should
not be related to different temporal database formats.
Can you access the database with the sqlite3 command directly?
sqlite3 /grassdata/latlong/ecad100_climate/tgis/sqlite.db
yes, I can see the tables and they seems coming from a temporal dataset 
Best regards
Soeren
--
ciao
Luca
http://gis.cri.fmach.it/delucchi/
www.lucadelu.org
Hi Luca,
is it possible that the path to the location has changed or that the
location was renamed?
Best regards
Soeren
2015-06-12 8:07 GMT+02:00 Luca Delucchi <lucadeluge@gmail.com>:
On 11 June 2015 at 21:54, Sören Gebbert <soerengebbert@googlemail.com> wrote:
Hi Luca,
Hi Soeren,
i did not change the database structure of the temporal framework recently.
The exception seems to be from the sqlite3 backend, hence it should
not be related to different temporal database formats.
Can you access the database with the sqlite3 command directly?
sqlite3 /grassdata/latlong/ecad100_climate/tgis/sqlite.db
yes, I can see the tables and they seems coming from a temporal dataset
Best regards
Soeren
--
ciao
Luca
http://gis.cri.fmach.it/delucchi/
www.lucadelu.org
On 25 June 2015 at 00:05, Sören Gebbert <soerengebbert@googlemail.com> wrote:
Hi Luca,
Hio Soeren
is it possible that the path to the location has changed or that the
location was renamed?
mmm I don't think so, but I'm not sure.
The path to db it seems correct using t.connect -l, do you have any
trick to solve this problem?
Best regards
Soeren
--
ciao
Luca
http://gis.cri.fmach.it/delucchi/
www.lucadelu.org
Hi Luca,
i just committed a patch in SVN that can handle modified location path's.
Please make an update of grass7.1 and then call t.connect -d in the
specific location/mapset to reset the default connection, which is
mapset specific.
I hope the temporal framework will find the correct database again.
Best regards
Soeren
2015-06-25 11:30 GMT+02:00 Luca Delucchi <lucadeluge@gmail.com>:
On 25 June 2015 at 00:05, Sören Gebbert <soerengebbert@googlemail.com> wrote:
Hi Luca,
Hio Soeren
is it possible that the path to the location has changed or that the
location was renamed?
mmm I don't think so, but I'm not sure.
The path to db it seems correct using t.connect -l, do you have any
trick to solve this problem?
Best regards
Soeren
--
ciao
Luca
http://gis.cri.fmach.it/delucchi/
www.lucadelu.org
On Thu, Jun 25, 2015 at 5:53 AM, Sören Gebbert <soerengebbert@googlemail.com
wrote:
Hi Luca,
i just committed a patch in SVN that can handle modified location path's.
Thanks Soeren, I think I actually hit the issue before.
Please make an update of grass7.1 and then call t.connect -d in the
specific location/mapset to reset the default connection, which is
mapset specific.
I hope the temporal framework will find the correct database again.
Best regards
Soeren
2015-06-25 11:30 GMT+02:00 Luca Delucchi <lucadeluge@gmail.com>:
> On 25 June 2015 at 00:05, Sören Gebbert <soerengebbert@googlemail.com>
wrote:
>> Hi Luca,
>
> Hio Soeren
>
>> is it possible that the path to the location has changed or that the
>> location was renamed?
>>
>
> mmm I don't think so, but I'm not sure.
> The path to db it seems correct using t.connect -l, do you have any
> trick to solve this problem?
>
>> Best regards
>> Soeren
>>
>
> --
> ciao
> Luca
>
> http://gis.cri.fmach.it/delucchi/
> www.lucadelu.org
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
On 25 June 2015 at 11:53, Sören Gebbert <soerengebbert@googlemail.com> wrote:
Hi Luca,
Hi Soeren,
i just committed a patch in SVN that can handle modified location path's.
Please make an update of grass7.1 and then call t.connect -d in the
specific location/mapset to reset the default connection, which is
mapset specific.
I hope the temporal framework will find the correct database again.
yes now it works!
Best regards
Soeren
Thanks a lot
--
ciao
Luca
http://gis.cri.fmach.it/delucchi/
www.lucadelu.org