extract DbConn from PlumeRocket #805
无评审员
标签
未选择标签
A: API
A: Backend
A: Federation
A: Front-End
A: I18N
A: Meta
A: Security
Build
C: Bug
C: Discussion
C: Enhancement
C: Feature
Compatibility
Dependency
Design
Documentation
Good first issue
Help welcome
Mobile
Rendering
S: Blocked
S: Duplicate
S: Incomplete
S: Instance specific
S: Invalid
S: Needs Voting/Discussion
S: Ready for review
Suggestion
S: Voted on Loomio
S: Wontfix
未选择里程碑
暂无项目
未指派成员
2 位参与者
通知
到期时间
未设置到期时间。
依赖工单
没有设置依赖项。
引用:Plume/Plume#805
正在加载…
添加表格
在新工单中引用
没有提供说明。
删除分支 "igalic/Plume:refactor/extract-dbconn"
删除分支是永久的。虽然已删除的分支在实际被删除前有可能会短时间存在,但这在大多数情况下无法撤销。是否继续?
in the following Pull Request, we'lle extract
DbConn
fromPlumeRocket
, as suggested in #797#[database]
to implement ourDbConn
#[database]
's connection setup, retaining our owninit_pool()
andConnectionCustomization
!DbConn
in asref
instead ofCopy
ing it around.@ -41,3 +12,1 @@
&self.0
}
}
#[database("plume")]
I think you'll have to edit
plume-models/src/config.rs
so that Rocket knows the URL of this "plume" database.yesno… we want to retain our
ConnectionCustomization
, so we're keeping our owninit_pool()
.9c7af7dcd4
,至3d8785e97b
比较add rocket_contrib as dependency为 extract DbConn from PlumeRocketThis will help with the
async
migration, as we're currently passing all of PlumeRocket around asref
, which means that it ends up sitting somewhere in a function, until it's.await
ed.This can create lead us into a big mess, which may be impossible to untangle, so this should help not running into that to begin with.
closing in favour of #813
合并请求已关闭