Handle "soft deletes"

gaboluque2 years ago

6

• 

  alessiogr

  2 years ago

  Heya! What do you mean with "omit"? Not display those in the API response?

• 

  jmikrut

  2 years ago

  you could add a custom field that called

  deleted

  and then write access control to return a query constraint like the following:

  
  
  

  {
    deleted: {
      not_equals: true
    }
  }

  
  
  

  that way any posts marked as deleted will still exist in the database, but will automatically be omitted from all API responses

• 

  gaboluque2 years ago

  @360823574644129795

  what I mean by omit is exactly what

  @364124941832159242

  is suggesting. Having records "deleted", never queried in the DB, but still there.

  
  
  

  I ended up adding a

  beforeOperation

  hook, with something like this:

  
  
  

    return { ...args, where: { ...args.where, status: { not_equals: UserStatus.DELETED, ...args.status } } }

  
  
  

  Although I'm not sure how this will affect other queries 👀 . WDYT? Maybe the Access Control is more performant?

• 

  dribbens

  2 years ago

  As long as you have an index on UserStatus, it will be very performant.

• 

  jmikrut

  2 years ago

  i would use access control instead of a

  beforeOperation

  hook but honestly either is the same performance. and yes, as dan said, make sure to index the field 👍

• 

  gaboluque2 years ago

  Thanks guys!