glime-ai[bot]
commented
2 months ago To handle migrations for an Oracle database with Elsa 3.1, you would typically need to generate your own migrations since the current release does not include an Oracle Entity Framework project or migration scripts for Oracle. This is often the case when a specific database provider is not directly supported by the library or framework you are using.
However, it's important to check the official documentation or reach out to the maintainers of Elsa Workflows to see if there are plans to add Oracle support in the future. If Oracle support is planned for a future release, you may decide to wait for that release or contribute to the project to help add the necessary support.
If you need to proceed with creating your own migrations, you would use the standard Entity Framework Core tools to generate migrations based on your DbContext and model configurations. You would then need to adjust the generated migration code to be compatible with Oracle 11g, considering any specific SQL syntax or database features that are unique to Oracle.
Remember to test your migrations thoroughly in a development environment before applying them to a production database to ensure they work as expected.
For the most accurate and up-to-date information, I recommend checking the official Elsa Workflows GitHub repository and discussions for any announcements or community-contributed solutions regarding Oracle database support.
This comment was generated by Glime.
sfmskywalker
AlexK555
Previous version v2 had migration for oracle database. Current release doesn't have Oracle EF project anymore, also generate-migrations-initial copy.sh doesn't have Oracle option. How to go with migration for Oracle database ? Is it expected to generate our own migration for version 3.1 or it is planned to add it in future?