Hi everyone,
I’m exploring the possibility of using Oracle Edition-Based Redefinition (EBR) for managing schema changes in a Camunda 7 embedded setup. Specifically, I’m looking to apply EBR to Camunda’s core tables to ensure smooth transitions between schema versions without downtime.
I’m curious to know if anyone has:
- Tried implementing EBR for Camunda tables?
- Encountered challenges or limitations while setting this up?
- Found best practices for maintaining compatibility between editions during workflow execution?
Any insights, tips, or examples from your experience would be highly appreciated!
Thanks in advance for sharing your thoughts.