Open jj0hns0n opened 10 years ago
This is a GeoGit error. Might be that the table already exists? I could add an overwrite option to the exportsl method
If the table does not exist, the problem is then on the GeoGit side. Can you check that the command passed to GeoGit is correct and that it also fails when used directly on the CLI?
Im trying to export a tree to a spatialte database and getting the following error.
pg_repo.exportsl("HEAD", "roads", "/home/vagrant/data/sl/roads_exported.sqlite")
Traceback (most recent call last): File "test_geogit_pg.py", line 92, in
pg_repo.exportsl("HEAD", "roads", "/home/vagrant/data/sl/roads_exported.sqlite")
File "/home/vagrant/geogit-py/src/geogitpy/repo.py", line 366, in exportsl
self.connector.exportsl(_resolveref(ref), path, database, user, table)
File "/home/vagrant/geogit-py/src/geogitpy/cliconnector.py", line 428, in exportsl self.run(commands) File "/home/vagrant/geogit-py/src/geogitpy/py4jconnector.py", line 123, in run return _runGateway(commands, self.repo.url) File "/home/vagrant/geogit-py/src/geogitpy/py4jconnector.py", line 82, in _runGateway raise GeoGitException("\n".join(output)) geogitpy.geogitexception.GeoGitException: Cannot create new table in database