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

Database adapter, PostgreSQL support #85

Open
avelino opened this issue Feb 18, 2019 · 8 comments
Open

Database adapter, PostgreSQL support #85

avelino opened this issue Feb 18, 2019 · 8 comments
Labels
enhancement New feature or request

Comments

@avelino
Copy link

avelino commented Feb 18, 2019

No description provided.

@cdujeu cdujeu added the enhancement New feature or request label Mar 6, 2019
@bsinou
Copy link
Collaborator

bsinou commented Jul 4, 2019

Hi,

We have been working on a first PoC a few weeks ago, (see branch pgsql-poc) and had been able to start Cells with service pydio.grpc.acl backed by a PostgreSQL DB.

This helped us to have a better overview of what has to be done and there is some work at hand, that is mainly:

  • rewrite all DB creation / migration scripts for each microservice that is backed by a DB with PGSQL specific syntax
  • adapt our store procedures that are using MySQL specific place holders, for this we must either:
    • rewrite all parametrized stored procedure using Goqu
    • choose a strategy (Qoqu might also come handy here) to translate the stored procedures either once or dynamically during initphase of the service from MySQL syntax to PGSQL syntax: the place holder in prepared statements depend on the adapter (e.g. ? mysql, $1 postgres, ? sqlite3)
  • enrich our non regression tests to insure switching to PGSQL does not break anything
  • benchmark pretty big systems backed with PGSQL to insure it holds the load. This benchmarking would also help us to gather some best practices and PGSQL specific fine tuning tips.

We do not really have the time to do this alone by ourselves in a very near future, yet we think this is a good candidate for a community driven effort to which we would take part.

Would anyone be interested to take part in the process?

@LNAhri
Copy link

LNAhri commented Sep 25, 2021

Simillar to this Point: #319.

Also did you guys heared from gorm ? Pretty good library for also handling multiple DB backends.
https://gorm.io/

@DUOLabs333
Copy link

The POC has not been updated in quite a while. Is it able to just be rebased on master?

@cdujeu
Copy link
Member

cdujeu commented Apr 11, 2022

hello! very probably ... not.
we have not put much effort on that PG support lately.

@elhananjair
Copy link

Postgres is very popular now a days and easy to configure it would be best if it available as an option

@bsinou
Copy link
Collaborator

bsinou commented May 21, 2024

We are working on it. Stay tuned.

@aleksasiriski
Copy link

Any updates on this?

@cdujeu
Copy link
Member

cdujeu commented Sep 5, 2024

yep - it's going well in the current development cycle. Target for v5, ~mid november

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

7 participants