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

Naming Conventions · Changes

Page history
Edited online authored Feb 01, 2019 by Andrea Pavlovic's avatar Andrea Pavlovic
Hide whitespace changes
Inline Side-by-side
Naming-Conventions.md
View page @ 36c5acdf
......@@ -10,6 +10,8 @@ define a database, had to be re-named.
module - schema
entity - table
attribute - column
client - role/user
agenda - user/permission group
## Transitions
......@@ -18,10 +20,14 @@ A transition is a change in a database. The basic set are "read","create",
Custom transitions may be based on any of the basic ones and may define
* type
* pre-state
* post-state
* type
* binding-reference
* notification
As well as which of the attributes of the entity may be changed with
this transition.
\ No newline at end of file
this transition.
By listing a transition in the agenda section as an agenda-binding, that
agenda gets the right to that transition.
\ No newline at end of file
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