Loading TOC...
Messages and Codes Reference Guide (PDF)

Messages and Codes Reference Guide — Chapter 33

TRGR Messages

TRGR-COLSCOPEURI

Message Text

Collection scope does not have trgr:uri

Cause

An attempt was made to create or update a trigger with a collection scope that was missing a uri element. The URI is required.

Response

Fix the application to provide a URI for the collection-scope.

TRGR-CONTENT

Message Text

Invalid Content

Cause

An invalid content element was supplied as the content parmeter when creating a trigger data event. Create the trgr:trigger-data-event content parameter using the API functions trgr:document-content, trgr:property-content, or trgr:any-property-content.

Response

Correct your code.

TRGR-CONTENTCOUNT

Message Text

Data event should only have one content

Cause

A trigger data event definition includes more than one content element.

Response

Remove all but one content element from your trigger definition. See trgr:trigger-data-event, or "Using Triggers to Spawn Actions" in the Application Developer's Guide.

TRGR-DATABASE

Message Text

Database does not exist: variable1

Cause

A trigger definition contains an invalid database id, or an invalid database id was supplied to trgr:trigger-module

Response

Correct the code by supplying the id of an existing database in the trigger definition or to trgr:trigger-module.

TRGR-DIRSCOPE

Message Text

Directory scope missing trgr:uri and/or trgr:depth

Cause

The XML node describing the directory scope of a trigger data event definition does not include at least one of trgr:uri or trgr:depth.

Response

Use trgr:directory-scope to construct a valid directory scope definition to pass to trgr:trigger-data-event.

TRGR-DIRSLASH

Message Text

Directory URI must end with '/'

Cause

The directory URI in a trigger directory scope definition does not end with '/'. For example:

trgr:directory-scope("/must/end/with/slash", "infinity")

Response

Correct the directory URI to end with '/'. For example:

trgr:directory-scope("/must/end/with/slash/", "inifinity")

TRGR-DOCCONTENT

Message Text

Invalid Document Content

Cause

The content part of a data event trigger does not include a valid update kind, or the update kind passed to trgr:document-content is invalid. The update kind must be one of "create", "modify" or "delete".

Response

Correct your code to have a valid update kind. For details, see trgr:document-content.

TRGR-DOCSCOPEURI

Message Text

Document scope does not have trgr:uri

Cause

An attempt was made to create or update a trigger with a document scope that was missing a uri element. The URI is required.

Response

Fix the application to provide a URI for the document-scope.

TRGR-EMPTYNAME

Message Text

Trigger name not supplied

Cause

An attempt was made to create or update a trigger definition where the name of the trigger was empty.

Response

Fix the application to provide a non-empty trigger name.

TRGR-EVENT

Message Text

Invalid trigger event: variable1

Cause

An attempt was made to create or update a trigger with a unrecognized event type. The event needs to be either "data-event" or "database-online-event".

Response

Fix the application to define a recognized event type.

TRGR-NAME

Message Text

Bad trigger name: variable1

Cause

An attempt was made to create or update a trigger definition with a trigger name that does not meet the trigger schema's constraints.

Response

The trigger name should be a non-empty string.

TRGR-NODATABASE

Message Text

Database missing or emptyin trigger module

Cause

The definition of a trigger does not include a valid trigger module database id. For example, trgr:trigger-module was called with the id of a non-existent database.

Response

Correct the trigger definition by using a valid database id.

TRGR-PATH

Message Text

root missing or empty in trigger module

Cause

An attempt was made to create or update a trigger with an empty module path. The path must be a valid path to an XQuery module.

Response

Fix the application to provide a non-empty path.

TRGR-PROPCONTENT

Message Text

Invalid Property Content

Cause

An attempt was made to create or update a property-content trigger which was missing a property-name element. The property-name is required for a property-content trigger.

Response

Fix the application to include a property-name.

TRGR-ROOT

Message Text

root missing or empty in trigger module

Cause

An attempt was made to create or update a trigger whose module specification has an empty "root" element.

Response

Fix the application to include a non-empty "root" element.

TRGR-SCOPE

Message Text

Invalid event scope

Cause

An attempt was made to create or update a trigger using an unknown scope type. The scope should be "document-scope", "collection-scope", or "directory-scope".

Response

Fix the application to provide a proper scope type.

TRGR-SCOPECOUNT

Message Text

Data event should only have one scope

Cause

An attempt was made to create or update a trigger using a data-event with more than one scope defined.

Response

Fix the application to provide only one scope to the data event.

TRGR-TNEXISTS

Message Text

Trigger already exists: variable1

Cause

Attempt to create a new trigger with a name that is already in use by another trigger, or attempt to rename a trigger to a name that is already in use.

Response

Change the trigger name to one that is not in use.

TRGR-TRIGGERDNE

Message Text

Trigger does not exist: variable1

Cause

The trigger name supplied to trgr:get-trigger or the trigger id supplied to trgr:get-trigger-by-id does not represent a valid trigger.

Response

Correct the trigger name or id and re-try the operation.

TRGR-WHEN

Message Text

Invalid when: variable1

Cause

The value for the "when" part of a trigger definition is not one of "pre-commit" or "post-commit". For example, trgr:trigger-data-event was called with a "when" parameter that was not created by calling trgr:post-commit or trgr:pre-commit.

Response

Correct your code. For details, see "Using Triggers to Spawn Actions" in the Application Developer's Guide.

« Previous chapter
Next chapter »
Powered by MarkLogic Server 7.0-4.1 and rundmc | Terms of Use | Privacy Policy