Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Elsa 3.1 oracle migration support #5310

Open
AlexK555 opened this issue Apr 30, 2024 · 3 comments
Open

Elsa 3.1 oracle migration support #5310

AlexK555 opened this issue Apr 30, 2024 · 3 comments
Labels
elsa 3 This issue is specific to Elsa 3 enhancement New feature or request

Comments

@AlexK555
Copy link

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?

@AlexK555 AlexK555 added the enhancement New feature or request label Apr 30, 2024
Copy link

glime-ai bot commented Apr 30, 2024

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
Copy link
Member

Hi @AlexK555

Thank you for raising the question, I hadn't given it much thought. I'd be OK with adding Oracle. If you need it soon, then perhaps you'd be interested in submitting a PR?

@sfmskywalker sfmskywalker added the elsa 3 This issue is specific to Elsa 3 label May 10, 2024
@AlexK555
Copy link
Author

AlexK555 commented May 10, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
elsa 3 This issue is specific to Elsa 3 enhancement New feature or request
Projects
Status: No status
Development

No branches or pull requests

2 participants