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
I've changed UI components for each vertex and edge in my graph using Graph Editor. It does what I want to achieve and it's really good!
Now, I have some questions.
I have two users, root and admin. I made changes in root, but I notice that the changes doesn't apply to admin. I can make same changes using the Graph Editor for admin right now. But I will have multiple users pretty soon, and it concerns me how to tackle this issue.
How can I make sure that all users in my database view the same graph (with same fill, stroke, size, and etc)? Is there a one single configuration file I can change and apply to the graph view? I saw _studio.pcl file and it seems to contain information about graph config including fill, stroke, icon, and so on.
Any insight would be appreciated.
The text was updated successfully, but these errors were encountered:
configuration are per users. If you want to copy configuration from user to another you can run
this batch script
let cfg =selectfrom _studio whereuser.name='admin';
let usr =selectfrom OUser where name ='reader';
update _studio set type ="GraphConfig", config = $cfg[0].config ,user = $usr[0] UPSERT whereuser.name='reader';
if you want to apply a specific config from a user to all users you can use this
let cfg =selectfrom _studio whereuser.name='admin';
update _studio set type ="GraphConfig", config = $cfg[0].config;
Hi, I'm building a graph using OrientDB on AWS.
I've changed UI components for each vertex and edge in my graph using Graph Editor. It does what I want to achieve and it's really good!
Now, I have some questions.
I have two users, root and admin. I made changes in root, but I notice that the changes doesn't apply to admin. I can make same changes using the Graph Editor for admin right now. But I will have multiple users pretty soon, and it concerns me how to tackle this issue.
Any insight would be appreciated.
The text was updated successfully, but these errors were encountered: