A list of users is one of the types of GDB components together with maps, themes, tables, queries and style libraries. Along with other types of components the list of users takes part in the operation of GDB merging. All other copying operations do not affect the list of users.
Chapter 59 “Merging GDB” describes the page of copying wizard “Resolving conflicts of components”. This section describes how setting of copying of the list of users is performed on this page.
The line “Users” will be present in the pane of component types only when three conditions are met simultaneously:
source GDB contains a list of users (that is, access control is used for it);
the current user of source GDB has permissions to the list of users;
the current user of destination GDB also has permissions to the list of users or the destination GDB does not have a list of users.
An example of the page “Resolving conflicts of components” with selected type of components “Users” is shown at figure 87-8.
Figure 87-8. Resolving conflicts of components when merging lists of users
When the line “Users” is selected in the pane of component types, a list of users of source GDB is displayed in the pane of components. However, administrator of source GDB is present in the list only in the case if the list of users is absent in the destination GDB (otherwise, there is its own administrator there). In this situation the administrator of source GDB should be necessarily copied (it is impossible to select the menu item Do not Copy when setting the operation of merging GDB). In this way access control is set for destination GDB.
Context menu of the settings pane contains items Default, Rename and Do not Copy. All these items are performed for the user selected in the pane.
The item Default permits specifying default processing method (“Copy”) for selected user – copying the user of source GDB to destination GDB under the same name.
Processing method “Copy” is set for the user by default if the destination GDB does not have the user with the same name. If the destination GDB already has the user with the same name, in this case “Undefined” will be set in the column “Operation”.
The item Rename allows copying the user to destination GDB under another name. When selecting this item the system will request a new name for the user being copied. The new name will be indicated in the column “Name in destination”.
The item Do not Copy allows the system to refuse from copying selected user.
Permissions to components of merged destination GDB are set in the following way.
Users copied from source GDB retain their permissions to components copied from the source. These users do not get access to components of destination GDB existing before the operation of merging GDB, if the destination GDB contained a list of users before merging.
Users of destination GDB existing before the operation of merging GDB (with the exception of the current user and administrator) do not get access to components copied from source GDB.
For the current user of destination GDB the same permissions to copied components are set as for the current user of source GDB.
Administrator of destination GDB gets all permissions to copied components.