tenkoh

read, write: how about use some option pattern with request parameters?

1

Each request parameter such as ListParams have many fields. Users have difficulty to utilize them correctly. Split fields into required a nd optional will help them. ex) functional option pattern

Request parameters such as ListParams contain many fields. They have no comments on code, so users could hardly recognize whether a field is required or not (i.e. optional).

Close #74 Verify client has options to specify pin_expiry and next_event_wait, but there are no implementations. This PR has implemented them.

### What do you want to change? Thank you for an awesome tool! When I had tried a simple schema and a query for SQLite3, I got `relation "users" does...