Setup Diesel workflow for use in rest of project #24

Closed
opened 2021-04-15 10:38:04 +02:00 by Jef Roosens · 0 comments
  • We'll use Diesel as the ORM for our database

We need the following:

  • Method for handling migrations (e.g. project-wide or per feature?)
  • Ability to pass database connections to routes when needed (included in Rocket I think)

We can give each feature its own database schema, and handle a lot of the data checking inside the database.

* We'll use Diesel as the ORM for our database We need the following: - [x] Method for handling migrations (e.g. project-wide or per feature?) - [x] Ability to pass database connections to routes when needed (included in Rocket I think) We can give each feature its own database schema, and handle a lot of the data checking inside the database.
Jef Roosens added this to the Fej 1.2.0 - Curse of the Forge milestone 2021-04-15 10:38:04 +02:00
Jef Roosens added the
enhancement
label 2021-04-15 10:38:04 +02:00
Jef Roosens self-assigned this 2021-04-15 10:38:04 +02:00
Jef Roosens added this to the Fej 1.2 - Curse of the Forge project 2021-04-15 10:38:04 +02:00
Jef Roosens added a new dependency 2021-04-15 10:38:18 +02:00
Jef Roosens added a new dependency 2021-04-15 10:40:27 +02:00
Jef Roosens modified the milestone from Fej 1.2.0 - Curse of the Forge to Fej 1.0.2 2021-04-17 09:36:42 +02:00
Jef Roosens modified the project from Fej 1.2 - Curse of the Forge to Fej 1.0.2 2021-04-17 09:44:09 +02:00
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Reference: Chewing_Bever/fej#24
There is no content yet.