If you have the enterprise enterprise edition, you could store each user’s data in a separate graph. You will need to track each user’s graph and switch to that graph in your query.
@glilienfield Could you please tell more about this feature?
Also, I found this answer: Best way to store multiple graphs for different users - #2 by glilienfield
- Store each user’s graph in a separate database. You can have the database automatically selected for the user by using ‘home databases’ or maintain your own mapping and specify the database when you create the session.
Isn't it too heavy to create a new database for each dedicated user? Is there any information on how each db may affect performance / consume resources?