New epgsql release roadmap

[Sergey Prokhorov]

Looks like it's a good time for the next epgsql release:

- There is a lot of improvements and new features

- Last release was released more than half year ago

There is some not yet fixed / committed issues/PRs and I thing it will be good to fix them before release.

* Fix typespecs, related to date and time. https://github.com/epgsql/epgsql/pull/106 

* (Minor) Inconsistency in delete ... returning https://github.com/epgsql/epgsql/issues/86

Probably add extended 'with_transaction/3' https://github.com/epgsql/epgsql/pull/111

Currently changelog may look like:

* Streaming replication protocol support (epgsql may act like PostgreSQL slave) https://github.com/epgsql/epgsql/blob/devel/streaming.md

* Options now may be passed as map()

* More error extra data fields returned in #error{extra} http://www.postgresql.org/docs/current/interactive/protocol-error-fields.html

* Added `set_notice_receiver/2` function to dynamically change receiver for asynchronous notifications

* Asynchronous notifications receiver may be set to registered process name (atom)

* `get_cmd_status/1` function added**

* TODO: fixed return value of `DELETE ... RETURNING ..` in case when 0 rows was deleted (now returns `{ok, 0, Columns, []}` instead of `{ok, 0}`)

* Some typespecs fixed (TODO: #106)

* TCP socket implicitly closed when epgsql connection process terminates

** The main practical usecase is to detect if transaction was committed after COMMIT.

{ok, _, _} = epgsql:squery(C, "BEGIN").
{error, _} = epgsql:equery(C, "SELECT 1 / $1::integer", [0]).
{ok, _, _} = epgsql:squery(C, "COMMIT").
{ok, rollback} = epgsql:get_cmd_status(C).

[David Welton]

> Looks like it's a good time for the next epgsql release:
> - There is a lot of improvements and new features
> - Last release was released more than half year ago

+1 from me.

--
David N. Welton

http://www.welton.it/davidw/

http://www.dedasys.com/

[Сергей Прохоров]

Hey, Davidw (and others, if there are any). May you, please, review last 2 pull-requests before I can tag this release?

https://github.com/epgsql/epgsql/pull/115

https://github.com/epgsql/epgsql/pull/106

[Sergey Prokhorov]

So, finaly, epgsql 3.3.0 https://github.com/epgsql/epgsql/releases/tag/3.3.0

вторник, 29 ноября 2016 г., 16:48:37 UTC+3 пользователь Sergey Prokhorov написал:

[David Welton]

Excellent! Thanks for all your work on this!

> --
> 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.
> For more options, visit https://groups.google.com/d/optout.