anchor.diff:      public String name;
       public LocalDate birth;
       public Status status;
  -    
  +
       public static Person findByName(String name){
         return find("name", name).firstResult();
       }
  -    
  +
       public static List<Person> findAlive(){
         return list("status", Status.Alive);
       }
  -    
  +
       public static void deleteStefs(){
         delete("name", "Stef");
       }
  
positive.code: 
  == Transactions
  
  Make sure to wrap methods modifying your database (e.g. `entity.persist()`) within a transaction. Marking a 
  CDI bean method `@Transactional` will do that for you and make that method a transaction boundary. We recommend doing 
  so at your application entry point boundaries like your REST endpoint controllers.
  
  == Lock management
  
  Panache does not provide direct support for database locking, but you can do it by injecting the `EntityManager` in your entity (or `PanacheRepository`) and creating a specific method that will use the entity manager to lock the entity after retrieval. The entity manager can also be retrieved via `Panache.getEntityManager()`.
  
  The following example contains a `findByIdForUpdate` method that finds the entity by primary key then locks it. The lock will generate a `SELECT ... FOR UPDATE` query (the same principle can be used for other kinds of `find*` methods):
  
  [source,java]
  --
  
negative.code:     public LocalDate birth;
      public Status status;
  
      public static Person findByIdForUpdate(Long id){
        // get the EntityManager inside the entity
        EntityManager entityManager = Panache.getEntityManager();
  
        Person person = findById(id);
        //lock with the PESSIMISTIC_WRITE mode type : this will generate a SELECT ... FOR UPDATE query
        entityManager.lock(person, LockModeType.PESSIMISTIC_WRITE);
  