| 9 | |
| 10 | Consider the following examples: |
| 11 | * A long running semantic query has been started from the {{{ri}}} module. Until the query has not been finished, nobody can add files from the {{{ri}}} module nor from the web interface, but another semantic query or a dependency examination can be started from any interface. |
| 12 | |
| 13 | * Database synchronization has been started from the web interface. Until the synchronization has not been finished, nobody can run a semantic query, can add content to the database from any interface. |
| 14 | |
| 15 | A list of the groups of modifiers is given below. |
| 16 | Every operation, which belongs to one of the listed groups, is demonstrated by giving the corresponding function from the {{{ri}}} module. We note that all of the user interfaces of the !RefactorErl is supervised by the same job server, so the same rules apply to them. |
| 17 | * Managing the content of the database: |
| 18 | {{{#!erlang |
| 19 | ri:reset/0, ri:reset/1, % reset the database |
| 20 | ri:add/1, ri:add/2, % add content |
| 21 | ri:drop/1, % drop content |
| 22 | ri:backup/0, ri:backup/1, % make a backup |
| 23 | ri:undo/0, % undo |
| 24 | ri:restore/1, % restore previous backup |
| 25 | ri:database_synchronization/0, % synchronize the database |
| 26 | }}} |
| 27 | * Managing environmental nodes: |
| 28 | {{{#!erlang |
| 29 | ri:addenv/2, %add an env. |
| 30 | ri:delenv/1, %delete an env. |
| 31 | ri:setenv/2 %set an env. |
| 32 | }}} |
| 33 | * Managing graphs (advanced topic): |
| 34 | {{{#!erlang |
| 35 | ri:create_graph/1, % create a new graph |
| 36 | ri:rename_graph/2, % rename a graph |
| 37 | ri:load_graph/1, % load a graph |
| 38 | ri:delete_graph/1, % delete a graph |
| 39 | ri:delete_all_graphs/0 % delete all graphs |
| 40 | }}} |
| 41 | |