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

Move projects workbench column to projects_nodes table #5646

Open
1 of 3 tasks
Tracked by #5648
sanderegg opened this issue Apr 9, 2024 · 1 comment
Open
1 of 3 tasks
Tracked by #5648

Move projects workbench column to projects_nodes table #5646

sanderegg opened this issue Apr 9, 2024 · 1 comment
Assignees
Labels
a:storage issue related to storage service a:webserver issue related to the webserver service
Milestone

Comments

@sanderegg
Copy link
Member

sanderegg commented Apr 9, 2024

Current projects table contain a workbench column of JSON type.
This was an easy way out 7 years ago but is now a bottleneck in many ways such as:

  • no relations options between the node_id or other useful parts of the workbench and anywhere else in the DB,
  • very poor performance when one needs to go through the DB information (1 row of projects contains all the nodes, so changing one node implies always locking the whole project) for patching, deleting nodes,

Nevertheless changing this fact is not a "piece of cake", as the projects table is sadly used by many different parts of oSparc and from many different processes, among others: webserver, director-v2, storage, others??? and multiple test fixtures and probably also other tests

Tasks

Preview Give feedback
  1. a:database a:director-v2 a:webserver
    giancarloromeo
  2. a:webserver
    giancarloromeo
  3. t:maintenance
    giancarloromeo
@giancarloromeo
Copy link
Contributor

I will take care of this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
a:storage issue related to storage service a:webserver issue related to the webserver service
Projects
None yet
Development

No branches or pull requests

5 participants