Fixed issue with User database responses:
Added insertable to ensure compilation even though we dont use that trait
This commit is contained in:
parent
81e6fd0a13
commit
22a1fd1730
@ -7,19 +7,22 @@ pub struct Invite {
|
||||
pub uses: i32,
|
||||
}
|
||||
|
||||
#[derive(Serialize, Deserialize, Queryable, Debug)]
|
||||
|
||||
#[derive(Insertable)]
|
||||
#[table_name = "users"]
|
||||
pub struct User {
|
||||
pub userid: u64,
|
||||
pub username: String,
|
||||
pub struct InsertableUser {
|
||||
pub name: String,
|
||||
pub secret: String,
|
||||
pub date: u64,
|
||||
pub status: i32,
|
||||
}
|
||||
|
||||
#[derive(Insertable)
|
||||
// NOTE: Insertable is the only rls stop complaining at us about `table_name` not being found in scope
|
||||
// its dumb but its how we're going to compile this, with some dead code
|
||||
#[derive(Insertable, Serialize, Deserialize, Queryable, Debug)]
|
||||
#[table_name = "users"]
|
||||
pub struct InsertableUser {
|
||||
pub struct User {
|
||||
pub id: u64,
|
||||
pub name: String,
|
||||
pub secret: String,
|
||||
pub date: u64,
|
||||
|
Loading…
Reference in New Issue
Block a user