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.

Sign up for GitHub

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

Jump to bottom

Multiple procrastinate instances on the same DB: namespaces #391

Open
ewjoachim opened this issue Mar 26, 2021 · 1 comment
Open

Multiple procrastinate instances on the same DB: namespaces #391

ewjoachim opened this issue Mar 26, 2021 · 1 comment
Assignees
@sheb
Labels
Issue appropriate for: Occasional contributors 😉 This issue will be best tackled by people with a minimum of experience on the project Issue contains: Exploration & Design decisions 🤯 We don't know how this will be implemented yet Issue contains: Some documentation 📚 This issues involves writing some documentation Issue contains: Some Python 🐍 This issue involves writing some Python code Issue contains: Some SQL 🐘 This features require changing the SQL model Issue type: Feature ⭐️ Add a new feature that didn't exist before

Comments

@ewjoachim
Copy link
Member

We have the case where several projects sharing the same DB want to use procrastinate independently.

We're going to support namespaces. A nullable namespace column will be added to procrastinate_jobs. Each function will take namespace as an optional parameter, and restrict its results on namespaces. LISTEN queue names will contain the namespace.

Namespaces will be provided to the App by a constructor kwarg, and passed to the Connector that will inject it in every query.
@ewjoachim ewjoachim added Issue appropriate for: Occasional contributors 😉 This issue will be best tackled by people with a minimum of experience on the project Issue contains: Some SQL 🐘 This features require changing the SQL model Issue contains: Some documentation 📚 This issues involves writing some documentation Issue contains: Exploration & Design decisions 🤯 We don't know how this will be implemented yet Issue contains: Some Python 🐍 This issue involves writing some Python code Issue type: Feature ⭐️ Add a new feature that didn't exist before labels Mar 26, 2021
@ewjoachim
Copy link
Member Author

ping @k4nar FYI :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sheb sheb

Labels
Issue appropriate for: Occasional contributors 😉 This issue will be best tackled by people with a minimum of experience on the project Issue contains: Exploration & Design decisions 🤯 We don't know how this will be implemented yet Issue contains: Some documentation 📚 This issues involves writing some documentation Issue contains: Some Python 🐍 This issue involves writing some Python code Issue contains: Some SQL 🐘 This features require changing the SQL model Issue type: Feature ⭐️ Add a new feature that didn't exist before
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@sheb @ewjoachim