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

Re-architect sea-orm depedency #40

Closed
tyt2y3 opened this issue Feb 2, 2022 · 0 comments · Fixed by #41
Closed

Re-architect sea-orm depedency #40

tyt2y3 opened this issue Feb 2, 2022 · 0 comments · Fixed by #41
Assignees

Comments

@tyt2y3
Copy link
Member

tyt2y3 commented Feb 2, 2022

Okay so the culprit is that sea-orm and sea-schema each has a dependency on sea-query, currently stuck in a deadlock, and there is no way to upgrade one side without breaking the other side.

We definitely have to re-architect this before releasing. The problem is the API exposed sea-query symbols and that tied things together. Ideally, sea-schema should be able to use a different sea-query version internally from sea-orm without causing trouble.

The migrator should use the sea-query pubed by sea-orm, or ideally, not using the high level sea-query interface at all.

Originally posted by @tyt2y3 in #26 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants