CHANGES 4.9 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104
  1. In 4.1.0
  2. * Fix Erlang 21 `get_stacktrace/0` warnings
  3. * Fix broken backward-compatibility in `bpchar` datatype
  4. * Fix compatibility issues between the newest rebar3 and Erlang R16
  5. In 4.0.1
  6. * Minor build bug fixed
  7. In 4.0.0
  8. Changes:
  9. * Make epgsql commands pluggable (see pluggable_commands.md).
  10. Now we are not limited only by API functions provided by epgsql (equery/squery/prepared_query etc),
  11. but may create own commands as a plugins. Still, understanding of PostgreSQL network protocol needed
  12. to be able to do so.
  13. * Make epgsql datatype encoding/decdoding pluggable (see pluggable_types.md).
  14. Now we are able to add or tweak codecs for existing as well as custom PostgreSQL
  15. datatypes (like datetime, varchar, enum, arrays etc).
  16. XXX: Highly recommend to add `{codecs, []}` option to your epgsql:connect/X calls if you don't use
  17. PostGIS and hstore datatypes: this will reduce connection setup time.
  18. * epgsql internals had a huge refactoring (4,000 additions and 1,750 deletions for ~5500 LOC project).
  19. Code now is much more modular, documented and have a lot of internal typespecs. Performance
  20. improvements are also expected.
  21. * Now we try to use iolists as much as possible and avoid binary and string concatenations when ever possible.
  22. Expect noticeable performance improvements for large BYTEA / TEXT / VARCHAR / JSON / JSONB etc fields.
  23. * Extended and documented epgsql:with_transaction/3.
  24. Now it's possible to preserve original exception's stacktrace, finally!
  25. * macaddr and macaddr8 datatypes support added
  26. * Float datatype support was extended with `nan`, `minus_infinity`, `plus_infinity`
  27. * elvis code style check was added to our travis pipeline
  28. * Brand-new PostgreSQL 10 scram-sha-256 auth method added
  29. (see https://www.postgresql.org/docs/10/static/auth-methods.html#AUTH-PASSWORD and
  30. https://www.postgresql.org/docs/current/static/sasl-authentication.html)
  31. * A lot of typespecs were rewritten and lots of internal typespecs were added
  32. Incompatibilities:
  33. * Some unexpected performance issues may appear, but we expect performance improvements, especially
  34. for a large result sets (when a lot of rows are returned by a query) and for large string/json/blob
  35. query parameters
  36. * Undocumented epgsql:update_type_cache/2 API was changed
  37. * A lot of typespecs were updated. Some typespecs were deprecated or moved from epgsql.erl to other
  38. modules. So, some new dialyzer warnings might pop-up
  39. * Some new error messages might be returned, especially from epgsql:connect/X functions
  40. * Memory consumption per-connection might slightly grow because we maintain per-connection OID<->codec
  41. mapping table, which might be quite big in some cases. This also may produce bigger error_logger
  42. reports in case of epgsql connection process crashes.
  43. * Some exported .hrl files have been changed. #column{} and #statement{} record definitions were extended.
  44. * PostGIS users might be affected by cleanup of ewkb.erl and epgsql_geometry.hrl
  45. * Streaming replication users should pay extra attention. No tests were broken, but a lot of
  46. modifications were made to this code.
  47. * Passing integer / atom / float as a value of a text / varchar / bytea query parameter is now
  48. deprecated (so, `epgsql:equery(C, "SELECT $1::text", [my_atom])` will still work but is not recommended)
  49. * Redshift and CockroachDB users might expirience some problems. Please, report bugs!
  50. In 3.4.0
  51. * Use rebar3 as default build and test tool
  52. * Move tests to common test; launch test postgresql server from Erlang
  53. * Compatibility with Erlang 20
  54. * `ssl_options` connection option fixed
  55. * New types: int8range and int4range
  56. In 3.3.0
  57. * Streaming replication protocol support (epgsql may act like PostgreSQL slave)
  58. https://github.com/epgsql/epgsql/blob/devel/streaming.md
  59. * Connection options now may be passed as map()
  60. * More error extra data fields returned in #error{extra}
  61. http://www.postgresql.org/docs/current/interactive/protocol-error-fields.html
  62. * Prefer non-localized severity in #error{severity} when available
  63. * Added `set_notice_receiver/2` function to dynamically change receiver for asynchronous notifications
  64. * Asynchronous notifications receiver may be set to registered process name (atom)
  65. * `get_cmd_status/1` function added
  66. * Fixed return value of `DELETE ... RETURNING ..` in case when 0 rows were deleted
  67. (now returns `{ok, 0, Columns, []}` instead of `{ok, 0}`)
  68. * TCP socket implicitly closed when epgsql connection process terminates
  69. * Some typespecs fixed
  70. In 3.2.0:
  71. * #error.codename (more readable errors)
  72. * Redshift support (by allowing dynamic typecache update fail)
  73. * Aggregate small binary packets to one in epgsql_sock (network performance improvement)
  74. * Handle situations, when server initiate connection close
  75. * prepared_query APIs (useful when you need to execute one query many times with different parameters)
  76. * array of records type support
  77. * jsonb type support
  78. In 3.1.1:
  79. * It dialyzes happily now
  80. In 3.1.0:
  81. * Deal with int4range type.
  82. In 3.0.0:
  83. * Renamed everything to use the epgsql namespace.