Obsidian Tables: Difference between revisions
From Obsidian Scheduler
Jump to navigationJump to search
No edit summary |
No edit summary |
||
| Line 2: | Line 2: | ||
'''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. | ||
Obsidian can be configured to use a table prefix when creating its tables. See [[Advanced_Configuration|Advanced Configuration]] for full details. | |||
* custom_calendar | * custom_calendar | ||
Revision as of 02:38, 25 June 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.
Obsidian can be configured to use a table prefix when creating its tables. See Advanced Configuration for full details.
- custom_calendar
- 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_interrupt
- job_history_result
- job_running_host
- job_state
- notification
- notif_template
- notif_template_entity
- operations_parameter
- role
- semaphore
- sequence_manager
- suite_user
- user_cookie
- user_role
- workflow_script
