Add database object name configurability to support multiple instances and custom schemas and table names - #11
Open
ArHndotAgz wants to merge 2 commits into
Open
Add database object name configurability to support multiple instances and custom schemas and table names#11ArHndotAgz wants to merge 2 commits into
ArHndotAgz wants to merge 2 commits into
Conversation
added 2 commits
October 7, 2025 15:56
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This PR enhances Hangfire.Oracle.Core with full database object name configurability, allowing for multiple Hangfire instances in the same database and custom schema support.
Key Features
• Configure schema name via external configuration
• Support unique instance names to avoid conflicts
• Customize table names, sequences, and other database objects
• Run multiple Hangfire instances side-by-side in the same schema
Breaking Changes
• Configuration structure has changed to support the new naming options
• Existing implementations will need to provide configuration or adapt to new defaults
• Database migration may be required when upgrading from previous versions
Migration Guide
Users upgrading from previous versions will need to: