ProAI/eloquent-versioning

Issues

• ForceDelete model

  #21 opened 6 years ago
  2

• Find many solution.

  #27 opened 6 years ago by juanabascal
  0

• Does this work with MongoDB ? I am using https://github.com/jenssegers/laravel-mongodb

  #26 opened 6 years ago by VenkiRao
  0

• Overwrite `qualifyColumn` model method in order to make some relationship work on versioned model

  #25 opened 6 years ago by Mortred974
  0

• Multiple primary key

  #16 opened 6 years ago
  2

• New version should not be created if versionable columns are intact

  #23 opened 6 years ago
  0

• Add methods to update/delete specific version

  #2 opened 6 years ago by markusjwetzel
  1

• Cache latest version data in main table

  #3 opened 6 years ago by markusjwetzel
  1

• How to create new version only if something changed?

  #13 opened 7 years ago by UksusoFF
  2

• Redundant versioned column selects on already selected columns

  #12 opened 6 years ago by safakz
  1

• double inner join

  #15 opened 6 years ago by jemoreno
  1

• how to define relations

  #17 opened 6 years ago by jelmerbou
  2

• Problem with Not unique table/alias

  #4 opened 8 years ago by borisovish
  6

• Mass assignment update bug

  #1 opened 9 years ago by markusjwetzel
  1