Reorganise the DB Hierarchy

Database Management Reference Manual

Database Modification : Modify the Content of a DB : Reorganise the DB Hierarchy

You can reorganise the structure of the DB hierarchy, without elements being added to or removed from its contents, in either of two ways:

•

By rearranging the order of the Member List of a single element

•

By relocating an element to a different part of the hierarchy

In both cases elements and their offspring are transferred to new positions in the hierarchy. In the first case the element's owner remains unchanged, while in the second case the element's owner changes.

To rearrange the Member List of the Current Element, use one of the commands:

REOrder element_id

REOrder element_id BEFore list_position

REOrder element_id AFTer list_position

where element_id specifies an element which is to be moved (which must be a member of the Current Element) and where list_position may be specified in any of the ways described in Database Navigation and Query Syntax.

If list_position is omitted, the intended position is assumed to be immediately after the Current List Position.

For example, starting with the previous Member List:

Figure 4:3.

Example Member List

the command

REORDER /ELBO3

moves /ELBO3 to position 5, immediately following the Current List Position, giving the new Member List

Figure 4:4.

Example of REORDER

Starting from either of the above configurations, the command

REORDER /ELBO3 BEFORE FIRST ELBO

moves /ELBO3 to position 3, immediately before /ELBO1, thus

Figure 4:5.

Example of REORDER

To insert an existing element into the Member List of the Current Element, when it is not already a member of that list, use one of the commands

INCLude element_id

INCLude element_id BEFore list_position

INCLude element_id AFTer list_position

where element_id specifies an element which is to be moved (which may be anywhere within the DB hierarchy as long as it is at an appropriate level) and where list_position may be specified in any of the ways described in Database Navigation and Query Syntax.

If list_position is omitted, the intended position is assumed to be immediately after the Current List Position.

For example, starting with the simple hierarchy

Figure 4:6.

Example Hierarchy

the command

INCLUDE /PIPE2

moves /PIPE2 (and all its offspring) to the position immediately following the Current List Position. Ownership of /PIPE2 passes from /ZONE2 to /ZONE1, resulting in the new hierarchy

Figure 4:7.

Example Hierarchy after INCLUDE /PIPE2 command