Dear all, JFYI i have updated the temporal framework in grass7.1 trunk (last commit is r62000) to support distributed temporal databases. The new default behavior is that sqlite3 based temporal databases will be created in the current mapset. The temporal framework takes care of which mapset specific temporal database should be used for data access. Existing locations with temporal databases should work as usual.
However, at the moment this works only with sqlite3 databases. Using several different postgresql database backends is untested. Mixing of sqlite and postgresql temporal databases in a single location is not possible. Some API changes were necessary to implement maspet specific temporal database management. I did not tested yet the temporal related GUI modules and code. Be aware that the temporal framework and the related modules in grass trunk (7.1 svn version) are highly experimental and should not be used in production. The new approach limits the use of SQL where and order statements in t.list. These statements will be performed for each temporal database, but not for the output of all databases together. Best regards Soeren _______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
