Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SurveyCTO: separate client data into Postgres databases #27

Open
TAnas0 opened this issue Feb 26, 2021 · 0 comments
Open

SurveyCTO: separate client data into Postgres databases #27

TAnas0 opened this issue Feb 26, 2021 · 0 comments
Labels
3 Not so complex, requiring a relatively good amount of effort and time to fix airflow enhancement New feature or request

Comments

@TAnas0
Copy link

TAnas0 commented Feb 26, 2021

The data imported from SurveyCTO into PostgreSQL is being saved into the default database. This can become unmanageable and may cause conflicts, when 2 servers have 2 forms of the same name for example

For the sake of isolation, create a dedicated PostgreSQL database for each SurveyCTO integration.
Also, deleting a client's data will be cleaner and less risky in the future.
This can maybe help in managing access to the loaded data in the future.

Acceptance Criteria
When a SurveyCTO server is hooked, create a dedicated PostgreSQL database.
Forms loaded as tables will be inside said database.

@TAnas0 TAnas0 self-assigned this Feb 26, 2021
@TAnas0 TAnas0 added the 3 Not so complex, requiring a relatively good amount of effort and time to fix label Feb 26, 2021
@andrewtpham andrewtpham added the enhancement New feature or request label Apr 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3 Not so complex, requiring a relatively good amount of effort and time to fix airflow enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants