The Essential Project Forum

If we make changes in a Protege 3.5 multiuser client to the data in an instance’s slot/property (for example an Individual_Business_Role instance Description) as far as we can see that change instantly shows up on all Protege 3.5 multiuser clients connected to the server. However, it is not in the MySQL table supporting that multiuser Protege 3.5 when we search the corresponding table with MySQL Workbench. The original unmodified version shows up on such a search. However, we also observe that the change is permanent and is there even if everything is restarted. But even after such a restart we cannot see the change in the MySQL database, only on the Protege 3.5 multiuser clients.

Guidance please on what we are missing in the storage piece of the Protege 3.5 multiuser architecture.

Thanks in advance, Bill

Hi Bill,

That the changes you’re making are seen in the clients and persist across system restarts shows that everything is working correctly.

Where it is stored is harder to work out as Protege will allocate it dynamically when you create the new slot. Although you can persist the repositories in a relational database, Protege does not use a relational model. Sorry that doesn't help much but the repository is managed in the database in a very normalised approach and it really doesn’t make sense to be interacting directly with the underlying MySQL.

Jonathan