anchor.diff:    in an unnamed portal on the server.
   . Send an EXECUTE message to read all the results from the portal.
   
  -There are a lot of PostgreSQL data types, but few primative data types in
  +There are a lot of PostgreSQL data types, but few primitive data types in
   Python. A PostgreSQL data type has to be assigned to each query parameter,
  -which is impossible to work out in all cases because, say, a Python
  -`int` could be any of the PostgreSQL integer types. pg8000's solution to this
  -problem is to send every parameter with the PostgreSQL type `unknown`. This
  +which is impossible to work out in all cases because. pg8000's solution to this
  +problem is to send some parameters with the PostgreSQL type `unknown`. This
   forces the server to make a guess about the type. It's fairly good at doing
   this, so most queries '`just work`'. However, sometimes you may need to do an
   explicit cast in the SQL query to get things to work.
  
positive.code: | uuid                              | binary
  |===
  
  Since pg8000 uses prepared statements implicitly, there's nothing to be gained
  by using them explicitly with the SQL PREPARE, EXECUTE and DEALLOCATE keywords.
  In fact pg8000 won't work for parameterized EXECUTE statements, because the
  server is unable to infer the types of the parameters for an EXECUTE statement.
  
  
  == API Docs
  
negative.code: 
  | None                              | binary
  | bool                              | binary
  | int                               | binary
  | float                             | binary
  | datetime.date                     | text
  | datetime.time                     | text
  