anchor.diff:  | 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.
  +* 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 in some cases pg8000 won't work for parameterized EXECUTE
  +  statements, because the server is unable to infer the types of the
  +  parameters for an EXECUTE statement.
  +
  +* PostgreSQL has +/-infinity values for dates and timestamps, but Python does
  +  not. Pg8000 handles this by returning +/-infinity strings in results, and in
  +  parameters the strings +/- infinity can be used.
  +
  +* PostgreSQL dates/timestamps can have values outside the range of Python
  +  datetimes. These are handled using the underlying PostgreSQL storage method.
  +  I don't know of any users of pg8000 that use this feature, so get in touch if
  +  it affects you.
  +
  +* Pg8000 can't handle a change of `search_path`, so statements like `set schema
  +  'value';` may cause subsequent statements to fail. This is because pg8000
  +  will use a prepared statement for a previously executed query, and this
  +  prepared statement won't be aware of any change in `search_path`.
   
   
   == API Docs
  
positive.code: 
  | None                              | binary
  | bool                              | binary
  | int                               | text
  | float                             | binary
  | datetime.date                     | text
  | datetime.time                     | text
  
negative.code: |===
  
  
  [[_theory_of_operation]]
  == Theory Of Operation
  
  