anchor.diff:  
   If for whatever reason, the aforementioned solution is deemed unacceptable, there are alternatives.
   
  -First, you can create a BSON Codec which will be automatically registered by Quarkus and will be used instead of the `PojoCodec`.
  +First, you can create a BSON Codec which will be automatically registered by Quarkus and will be used instead of the `PojoCodecProvider`.
   See this part of the documentation: link:mongodb#simplifying-mongodb-client-usage-using-bson-codec[Using BSON codec].
   
  -Another option is to use the `@BsonCreator` annotation to tell the `PojoCodec` to use the Kotlin data class default constructor,
  +Another option is to use the `@BsonCreator` annotation to tell the `PojoCodecProvider` to use the Kotlin data class default constructor,
   in this case all constructor parameters have to be annotated with `@BsonProperty`: see link:{mongodb-doc-root-url}/bson/pojos/#supporting-pojos-without-no-args-constructors[Supporting pojos without no args constructor].
   
   This will only work when the entity extends `PanacheMongoEntityBase` and not `PanacheMongoEntity`, as the ID field also needs to be included in the constructor.
  
positive.code: But this type of class comes with some limitations: all fields needs to be initialized at construction time or be marked as nullable,
  and the generated constructor needs to have as parameters all the fields of the data class.
  
  MongoDB with Panache uses the `PojoCodec`, a MongoDB codec which mandates the presence of a parameterless constructor.
  
  Therefore, if you want to use a data class as an entity class, you need a way to make Kotlin generate an empty constructor.
  To do so, you need to provide default values for all the fields of your classes.
  
negative.code: 
  NOTE: Annotating with `@MongoEntity` is optional. Here the entity will be stored in the `ThePerson` collection instead of the default `Person` collection.
  
  MongoDB with Panache uses the link:{mongodb-doc-root-url}/bson/pojos/[PojoCodecProvider] to convert your entities to a MongoDB `Document`.
  
  You will be allowed to use the following annotations to customize this mapping:
  
  