Allow storing outputs in database#371
Draft
janpisl wants to merge 21 commits intogeopython:dev-jobqueue-oldfrom
Draft
Allow storing outputs in database#371janpisl wants to merge 21 commits intogeopython:dev-jobqueue-oldfrom
janpisl wants to merge 21 commits intogeopython:dev-jobqueue-oldfrom
Conversation
Implement functionality for storing output data from run processes in a PostgreSQL or SQLite database
Collaborator
|
@janpisl Please check the travis build. There is an import error: ... and pep8 is failing. |
Author
|
Hi, @cehbrecht , thank you for pointing this out. I have edited my code so it
passes the test.
…On Mon, Aug 13, 2018 at 3:31 PM, MacPingu ***@***.***> wrote:
@janpisl <https://github.com/janpisl> Please check the travis build.
There is an import error:
File "/home/travis/build/geopython/pywps/pywps/inout/storage/db/sqlite.py", line 11, in <module>
from . import DbStorage
ImportError: cannot import name 'DbStorage'
... and pep8 is failing.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#371 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AexTMxKt0LP24khknXZezia_5kmk6ziJks5uQX_AgaJpZM4V6DwB>
.
|
Collaborator
|
@janpisl I have tested this PR with my Emu processes and I run into an exception (test with Python 3.6): I tried this with the Emu chomsky process. But this exception happens with every process having a complex output. I have used as config: Currently you have set |
Author
|
@cehbrecht thank you. i will look into it. |
Collaborator
|
@janpisl Please have also a look on the codacy check (see link above next to travis). The complains on the tests can be skipped. |
added 8 commits
September 24, 2018 12:56
Copy vector data to a schema specified in cfg instead of public schema.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Implement functionality for storing output data from run processes in a PostgreSQL or SQLite database
Overview
This extension allows output data from run processes to be stored in a PostgreSQL or SQLite database. This extension can be enabled in the configuration (section "server", option "store_type"; when set to "db", the extension is active). Credentials for connecting to the database are found in the (new) section "db".
Contribution Agreement
(as per https://github.com/geopython/pywps/blob/master/CONTRIBUTING.rst#contributions-and-licensing)
I'd like to contribute extension Database Output Storage to PyWPS. I confirm that my contributions to PyWPS will be compatible with the PyWPS license guidelines at the time of contribution.