mirror of
https://github.com/lldap/lldap.git
synced 2026-04-25 08:15:52 +03:00
[PR #382] [MERGED] server,app: migrate to sea-orm #710
Labels
No labels
backend
blocked
bug
cleanup
dependencies
docker
documentation
duplicate
enhancement
enhancement
frontend
github_actions
good first issue
help wanted
help wanted
integration
invalid
ldap
pull-request
question
rust
rust
tests
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/lldap-lldap#710
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/lldap/lldap/pull/382
Author: @nitnelave
Created: 11/25/2022
Status: ✅ Merged
Merged: 11/25/2022
Merged by: @nitnelave
Base:
main← Head:orm📝 Commits (2)
deb0e9eserver,app: migrate to sea-ormdd4e11eserver: move domain types to a separate file📊 Changes
45 files changed (+2375 additions, -1642 deletions)
View changed files
📝
Cargo.lock(+436 -148)📝
Cargo.toml(+4 -0)📝
app/Cargo.toml(+1 -0)📝
app/src/components/create_user.rs(+1 -4)📝
app/src/components/group_details.rs(+1 -1)📝
app/src/components/group_table.rs(+1 -1)📝
app/src/components/user_details_form.rs(+7 -7)📝
app/src/components/user_table.rs(+1 -1)📝
app/src/infra/cookies.rs(+5 -1)📝
schema.graphql(+1 -1)📝
server/Cargo.toml(+7 -19)📝
server/src/domain/error.rs(+3 -1)📝
server/src/domain/handler.rs(+8 -217)📝
server/src/domain/ldap/group.rs(+2 -2)📝
server/src/domain/ldap/user.rs(+6 -6)📝
server/src/domain/ldap/utils.rs(+2 -4)📝
server/src/domain/mod.rs(+2 -0)➕
server/src/domain/model/groups.rs(+53 -0)➕
server/src/domain/model/jwt_refresh_storage.rs(+35 -0)➕
server/src/domain/model/jwt_storage.rs(+36 -0)...and 25 more files
📄 Description
This PR migrates the project to use sea-orm instead of the lower-level sea-query.
The first-order effect is that it fixes #87 by being database-agnostic.
The second-order effect is that it makes complex queries (especially multi-table complex joins) easier to write. This will be especially useful for #67.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.