anchor.diff:  
   Note how we get back more information than what we sent to the server. We get all the values of all the fields. Where we didn't specify a value in submitted JSON the default was used.
   
  -There is also a read-only field called 'ddl' that contains a
  +There is also a read-only field called 'ddl' that contains a create table statement for your convenience.
   
   Table schema is described by four fields:
   
  
positive.code: 
  If column name doesn't end with '_id' then the referred table id is used as a field name (e.g. if foreign key column 'userid' references a table called 'users', then the field name will be called 'users' rather than 'userid'.
  
  In addition to row columns, the JSON item also contains synthetic fields for one-to-many relationships. These are references to items in other collections, representing tables with foreign keys referring to our table. There are corresponding columns in our table in this case. For these fields the name is equal to the other collection's id.
  
  For example, if there is a table 'messages' with column 'user_id' pointing to a table 'users', then each item in 'users' collection will contain a synthetic field named 'messages' containing a list of items corresponding to messages linked to that user.
  
  
negative.code: That would return messages starting with latest.
  
  
  Currently only targeted collection column fields can be specified for sorting. The following wouldn't work:
  
      ?sort=user.nick
  
  