anchor.diff:      @Id String number;
       User user;
       Address shipping;
  +    @AttributeOverrides({
  +        @AttributeOverride(name="name", column=@Column(name="delivery.provider"),
  +        @AttributeOverride(name="expectedDelaysInDays", column=@Column(name="delivery.delays")
  +    })
       DeliveryProvider deliveryProvider;
  +    CreditCardType cardType;
   }
   
   // default columns
  
positive.code:     String city;
  }
  
  @Embeddable
  public DeliveryProvider {
      @Column(name="delivery.provider")
      String name;
      @Column(name="delivery.delays")
      Integer expectedDelaysInDays;
  }
  ----
  
  
negative.code:         "provider": "Santa Claus Inc.",
          "delays": "1"
      }
      "network": "VISA",
      "cardType: {
          "merchant": "Amazon"
      }
  }
  ----
  
  If you share the same embeddable in different places, you can use JPA's +@AttributeOverride+
  to override columns from the embedding side.
  This is the case of +DeliveryProvider+ in our example.
  
  If you omit the dot in one of the columns, this column will not be part of the nested document.
  This is demonstrated by the +CreditCardType+.
  We advise you against it.
  Like crossing streams, it is bad form.
  This approach might not be supported in the future.
  ====
  
  ==== Associations
  