anchor.diff:  void insert(@BindBean User user);
   ----
   
  -Like `@BindMap`, you can qualify a bound bean with a prefix:
  +You can bind from the public fields of an object:
  +
  +[source,java]
  +----
  +@SqlUpdate("insert into users (id, name) values (:id, :name)")
  +void insert(@BindFields User user);
  +----
  +
  +Or you can bind from public, parameterless methods of an object:
  +
  +[source,java]
  +----
  +@SqlUpdate("insert into users (id, name) values (:functionThatReturnsTheId, :functionThatReturnsTheName)")
  +void insert(@BindMethods User user);
  +----
  +
  +Like `@BindMap`, `@BindBean` `@BindMethods` and `@BindFields` can have an optional prefix:
   
   [source,java]
   ----
   @SqlUpdate("insert into users (id, name) values (:user.id, :user.name)")
   void insert(@BindBean("user") User user);
  +//void insert(@BindFields("user") User user);
  +//void insert(@BindMethods("user") User user);
   ----
   
   [WARNING]
  -As in the Core API, neither `@BindMap` nor `@BindBean` support binding of
  +As in the Core API, neither `@BindMap`, `@BindBean`, `@BindFields` nor `@BindMethods` support binding of
   nested properties (e.g. `:user.address.street`).
   
   ==== @SqlQuery
  
positive.code:       .execute();
  ----
  
  Optionally, you can qualify each bound bean with a prefix. This can help remove
  ambiguity in situations where two or more bound beans have similar property
  names:
  
  
negative.code: void insert(@BindMap("user") Map<String, ?> map);
  ----
  
  You can bind from the properties of a Java Bean:
  
  [source,java]
  ----
  