-
-
Notifications
You must be signed in to change notification settings - Fork 37
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
Docs: adoption guide for existing SeaORM users #43
Comments
However, under the current setup. One has to modify existing SeaORM entities. I don't think it's ideal. Because it pollute the entity files and Ideally, we want to have a seperate files to implement the Thoughts? @tyt2y3 @karatakis |
We can approach the problem in 3 different ways:
|
It's probably just for me
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I think we need an "adoption guide" (feel free to rename it) for existing SeaORM users.
For example,
query_root.rs
has to be added as wellThe text was updated successfully, but these errors were encountered: