DropIndex

DropIndex

Attention!
Outdated! Indexmanager provides functions for index management

DropIndex(CX_xxxxx), DropIndex(CX_xxxxx, k)

parameters: Identifier of a class, number of a domain (default is k = 0)

Stack

Stack	Position	Description
Stack(In)	Top	Index path (as character string)
Stack(Out)	Top	-

The index of the k-th RootEP-Collection of a class (in the current layer) is removed. As with AddIndex the settings set with SetDomain are overridden by the parameter k(further hints ...). On the stack the index path is expected as a string.
The database index is deleted and the Index Manager is updated accordingly.

Removing an index may also result in address space overflow. This can be remedied by splitting the operation into multiple transactions:

Stack

Stack	Position	Description
Stack(In)	Top	]
		Index path (as character string)
		integer n
		OBJECTS_PER_TXN
		]
Stack(Out)		-

N objects are processed per transaction.

DropIndex(CX_xxxxx, access expression)

Stack

Stack	Position	Description
Stack(In)	Top	]
	Top 1	Parameters
		. . .
		the object
	Top-n	[
Stack(Out)		-

Collections also exist as an element (data field) of an object. In order to remove an existing index, there must be an object on the stack next to the index path, from which the collection is reached with the access expression (second parameter).

Here too, the multi-transaction variant can be requested with OBJECTS_PER_TXN n.