[SeaORM] migration guide for SeaQuery users
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 24
- Forks
- 68
- PR merge metrics
- No merged PRs in 30d
Description
Proposed by https://github.com/SeaQL/sea-orm/issues/1227#issuecomment-1314947381
Content
I think there are two types of use cases.
Mapping query result into struct
This serve as a way to execute any SeaQuery statement. And the query result of select statement can be mapped into a struct in Rust.
Basically, as mentioned in this cookbook article: https://www.sea-ql.org/sea-orm-cookbook/003-run-sea-query-statement-on-sea-orm.html
Full SeaORM with access to alter the SeaQuery statement
Setup SeaORM entity with sea-orm-cli or defining it manually.
Then, You can get a mutable reference of the SeaQuery select statement from sea_orm::Select by QuerySelect::query method. With that you can construct complex query.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked SeaORM cookbook article on running SeaQuery statements, then read the QuerySelect::query documentation. Create a migration guide covering both mapping query results into structs and using SeaORM while altering the SeaQuery statement; done means both use cases and the cited setup paths are explained.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100