Obsidian Tables: Difference between revisions

From Obsidian Scheduler
Jump to navigationJump to search
No edit summary
No edit summary
Line 3: Line 3:
'''Note:''' Since Obsidian does not run jobs within the same connection or transaction as your jobs, there is no real need to run Obsidian within the same database or schema as your own application(s), though you may wish to do so to facilitate maintenance.
'''Note:''' Since Obsidian does not run jobs within the same connection or transaction as your jobs, there is no real need to run Obsidian within the same database or schema as your own application(s), though you may wish to do so to facilitate maintenance.


* event_log
* event_subscriber
* event_subscriber
* event_subscription
* event_subscription
Line 8: Line 9:
* job_chain
* job_chain
* job_chain_mode
* job_chain_mode
* job_chain_mode_condition
* job_configuration
* job_configuration
* job_conflict_config
* job_conflict_config
Line 16: Line 18:
* job_running_host
* job_running_host
* job_state
* job_state
* log
* notification
* notification
* operations_parameter
* operations_parameter

Revision as of 13:22, 8 January 2013

Obsidian needs to create and manage the following tables in its target database. When sharing schemas between Obsidian and other applications, ensure there are no naming conflicts by reviewing this list.

Note: Since Obsidian does not run jobs within the same connection or transaction as your jobs, there is no real need to run Obsidian within the same database or schema as your own application(s), though you may wish to do so to facilitate maintenance.

  • event_log
  • event_subscriber
  • event_subscription
  • job
  • job_chain
  • job_chain_mode
  • job_chain_mode_condition
  • job_configuration
  • job_conflict_config
  • job_history
  • job_history_chain
  • job_history_error
  • job_history_result
  • job_running_host
  • job_state
  • notification
  • operations_parameter
  • role
  • semaphore
  • sequence_manager
  • suite_user
  • user_cookie
  • user_role
  • workflow_script