You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The content you are editing has changed. Please copy your edits and refresh the page.
Current
projects
table contain aworkbench
column of JSON type.This was an easy way out 7 years ago but is now a bottleneck in many ways such as:
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 testsTasks
workbench
fromprojects
toprojects_nodes
table 🗃️ #7010projects_nodes
DB table #7100The text was updated successfully, but these errors were encountered: