Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • A api
  • Project information
    • Project information
    • Activity
    • Members
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Wiki
    • Wiki
  • Activity
Collapse sidebar
  • ironapi
  • api
  • Wiki
  • Naming Conventions

Last edited by Andrea Pavlovic May 25, 2021
Page history

Naming Conventions

Home

  • Naming-Conventions
  • Transitions

Naming-Conventions

To avoid namespace clashes in the database, any reserved key words which define a database, had to be re-named.

  • module - schema
  • entity - table
  • instance - row
  • attribute - column
  • client - role/user
  • agenda - user/permission group
  • transition - an action (see Transitions and Transitions)

Transitions

A transition is an action in a database. The basic set are "read","create", "edit","delete".

Custom transitions may be based on any of the basic ones and may define

  • type
  • pre-state
  • post-state
  • binding-reference
  • notification

As well as which of the attributes of the entity may be changed with this transition.

By listing a transition in the agenda section as an agenda-binding, that agenda gets the right to that transition.

Clone repository
  • API
    • Available Endpoints
    • Changing Passwords
    • Form Input Types
    • Introduction
    • Logout
    • Plugins
    • Queries
    • Queries
      • Attributes
      • Context
      • Query Examples
      • Query Search Options
      • Referenced Instances
      • Saved Queries
    • Schema_Changes
    • Storing Files
View All Pages