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

unify resource_* with the configuration_* tables #400

Open
syjer opened this issue Feb 22, 2018 · 0 comments
Open

unify resource_* with the configuration_* tables #400

syjer opened this issue Feb 22, 2018 · 0 comments
Assignees
@syjer
Labels
enhancement
Milestone
2.0

Comments

@syjer
Copy link
Member

syjer commented Feb 22, 2018 •
edited
Loading

Currently the templates are saved in the resource_* tables, but, in theory, with some refactoring they coud be folded in the configuration_* .

Benefit: less tables, more coherent api.

Note: the configuration_* tables could be additionally folded in a single one.

Note2: we can use partial unique index for handling the uniqueness https://www.postgresql.org/docs/current/indexes-partial.html
@syjer syjer added this to the 2.0 milestone Feb 22, 2018
@syjer syjer self-assigned this Feb 22, 2018
@syjer syjer mentioned this issue May 18, 2018
Open
38 tasks
@syjer syjer modified the milestones: 2.0, 2.0-M3 Jun 4, 2019
@cbellone cbellone modified the milestones: 2.0-M3, 2.0-M4 Sep 2, 2020
@cbellone cbellone modified the milestones: 2.0-M4, 2.0 Jan 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@syjer syjer

Labels
enhancement
Projects
None yet
Milestone
2.0
Development

No branches or pull requests
2 participants
@syjer @cbellone