Obsidian Tables: Difference between revisions
From Obsidian Scheduler
Jump to navigationJump to search
m moved Espresso Tables to Obsidian Tables |
No edit summary |
||
| Line 1: | Line 1: | ||
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 | '''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_subscriber | * event_subscriber | ||
Revision as of 20:21, 21 February 2011
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_subscriber
- event_subscription
- job
- job_chain
- job_chain_mode
- job_configuration
- job_conflict_config
- job_history
- job_history_chain
- job_history_error
- job_history_result
- job_running_host
- job_state
- log
- notification
- operations_parameter
- role
- semaphore
- sequence_manager
- suite_user
- user_cookie
- user_role
- workflow_script
