anchor.diff:  changing a java entity the persistence layer will probably fail with its operations. For small changes (like name
   changes) you could manually update the database. For structural changes it's recommanded to export the data, delete
   the database, and import after the new creation. At the point where this procedure is too expensive you may be
  -enough experienced that you can manually update the database even for structural changes.+experienced enough to manually update the database even for structural changes.
positive.code: 	}
  ----
  The test method insert a simple test Object to the database. Then it will be read four times. Everytime the same SQL statement will be
  executed.
  
  The first read uses really plain SQL. You can copy the String and paste it in your favorite database explorer tool. I like that. It makes my
  life easy. And it's not half as dangerous as you might think. Of course when the name of the class changes the code will break. But
  
negative.code: The fourth definition uses a trick to further reduce the length of the query definition. It may be too much for you or your
  project. Again, discuss this with your team how would like to handle such things. You also may use an other method name for this trick.
  
  === Create tables
  Normally when starting an application the database for it already exists. The application should not create the tables
  every time it is started. For examples it is actually helpfull that the tables are created because otherwise the
  