New release 4.4.0 plan
31 views
Skip to first unread message
Sergey Prokhorov
Mar 9, 2020, 5:15:00 PM3/9/20
to Erlang epgsql Postgres driver use and development
There are quite a lot of changes
Release notes draft:
* Guards are now added to avoid silent integer truncation for numeric and
numeric range datatype codecs. So, an attempt to encode 100000 as `int2`
will now crash the connection instead of silently truncating it. #218
* `epgsql{a,i}:cancel/1` API was documented. #224
* Version of `execute_batch` that uses the same SQL query for each request
in a batch. Very convenient for batch-inserts. #209
* It's now possible to provide `#statement{}` to `prepared_query/3`. This way
of calling it eliminates extra `describe` round-trip thus making it more
efficient. #207
* Representation of SQL `NULL` is now fully configurable. You can choose what
set of Erlang terms should be interpreted as `NULL` and which term to use to
represent `NULL`s received from database. #212
* It's now possible to choose between 3 representations of a `hstore` datatype:
map(), jiffy-style objects (default) and proplist. It can also take `map()` as
input now. NULL value representation is also configurable. #217
* Edocs build was fixed. Just run `rebar3 edoc` and reference documentation for
all modules will be generated. But it's considered to be more "internal"
documentation for those who want to learn more about epgsql internals or
to do some hacking. It complements, but not replaces README. #214
* `epgsql:connect` `timeout` option is more strict now - it limits TCP and SSL
setup time as a whole. #223
* Test coverage report was enabled in CI. We will fail the build if coverage
falls below 55%. We hope to improve this metric over time. #208
* We now send `Terminate` message to the server when doing graceful connection
shutdown (as recommended by protocol). #219
* We found that `describe(_, portal, _)` API was broken since release v4.0.0, but
was not covered by tests. So now it was fixed and tests were added. #211
* Error code to error name conversion code was updated (see `#error.codename`).
Some new codes were added (mostly related to JSON datatypes) and one has changed.
So, if you were matching over `#error.codename` being
`invalid_preceding_following_size` you have to update your code. #210
* `#column{}` record is now fully documented. It was extended to
include `table_oid` and `table_attr_number` fields which point to the originating
database table of this column (if any). #205
* Extended timerange datatype support #204
* Some minor typos, datatype and CI fixes #199 #201 #206 #221
* Guards are now added to avoid silent integer truncation for numeric and
numeric range datatype codecs. So, an attempt to encode 100000 as `int2`
will now crash the connection instead of silently truncating it. #218
* `epgsql{a,i}:cancel/1` API was documented. #224
* Version of `execute_batch` that uses the same SQL query for each request
in a batch. Very convenient for batch-inserts. #209
* It's now possible to provide `#statement{}` to `prepared_query/3`. This way
of calling it eliminates extra `describe` round-trip thus making it more
efficient. #207
* Representation of SQL `NULL` is now fully configurable. You can choose what
set of Erlang terms should be interpreted as `NULL` and which term to use to
represent `NULL`s received from database. #212
* It's now possible to choose between 3 representations of a `hstore` datatype:
map(), jiffy-style objects (default) and proplist. It can also take `map()` as
input now. NULL value representation is also configurable. #217
* Edocs build was fixed. Just run `rebar3 edoc` and reference documentation for
all modules will be generated. But it's considered to be more "internal"
documentation for those who want to learn more about epgsql internals or
to do some hacking. It complements, but not replaces README. #214
* `epgsql:connect` `timeout` option is more strict now - it limits TCP and SSL
setup time as a whole. #223
* Test coverage report was enabled in CI. We will fail the build if coverage
falls below 55%. We hope to improve this metric over time. #208
* We now send `Terminate` message to the server when doing graceful connection
shutdown (as recommended by protocol). #219
* We found that `describe(_, portal, _)` API was broken since release v4.0.0, but
was not covered by tests. So now it was fixed and tests were added. #211
* Error code to error name conversion code was updated (see `#error.codename`).
Some new codes were added (mostly related to JSON datatypes) and one has changed.
So, if you were matching over `#error.codename` being
`invalid_preceding_following_size` you have to update your code. #210
* `#column{}` record is now fully documented. It was extended to
include `table_oid` and `table_attr_number` fields which point to the originating
database table of this column (if any). #205
* Extended timerange datatype support #204
* Some minor typos, datatype and CI fixes #199 #201 #206 #221
Any objections / concerns?
Sergey Prokhorov
Mar 12, 2020, 7:55:51 PM3/12/20
to Erlang epgsql Postgres driver use and development
Ok, so, it was released https://github.com/epgsql/epgsql/releases/tag/4.4.0
Note - now edocs are upploaded to https://hex.pm/packages/epgsql: https://hexdocs.pm/epgsql/ (but they are not targeting end users but rather "epgsql hackers").
понедельник, 9 марта 2020 г., 22:15:00 UTC+1 пользователь Sergey Prokhorov написал:
Marc Worrell
Mar 13, 2020, 3:35:57 AM3/13/20
to Sergey Prokhorov, Erlang epgsql Postgres driver use and development
Congratulations with this release.
Impressive list of additions and fixes.
Looking forward to start using it.
Didn’t know about the hex.pm edocs feature, need to look into that for other projects as well.
Cheers, Marc
--
You received this message because you are subscribed to the Google Groups "Erlang epgsql Postgres driver use and development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to epgsql+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/epgsql/6daa0c86-d0db-4377-afdc-3c8a24e28c50%40googlegroups.com.
David Welton
Mar 13, 2020, 12:10:27 PM3/13/20
to Marc Worrell, Sergey Prokhorov, Erlang epgsql Postgres driver use and development
Nice work, Sergey - thanks!
> To view this discussion on the web visit https://groups.google.com/d/msgid/epgsql/64284D88-E5DF-4812-8BEB-842DAC223FC6%40me.com.
--
David N. Welton
http://www.welton.it/davidw/
http://www.dedasys.com/
--
David N. Welton
http://www.welton.it/davidw/
http://www.dedasys.com/
Reply all
Reply to author
Forward
0 new messages