123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119 |
- In 4.2.1
- In 4.2.0
- DB passwords to be dumped to SASL crash log
- rebar on all supported OTP versions
- In 4.1.0
- In 4.0.1
- In 4.0.0
- Changes:
- Now we are not limited only by API functions provided by epgsql (equery/squery/prepared_query etc),
- but may create own commands as a plugins. Still, understanding of PostgreSQL network protocol needed
- to be able to do so.
- Now we are able to add or tweak codecs for existing as well as custom PostgreSQL
- datatypes (like datetime, varchar, enum, arrays etc).
- XXX: Highly recommend to add `{codecs, []}` option to your epgsql:connect/X calls if you don't use
- PostGIS and hstore datatypes: this will reduce connection setup time.
- Code now is much more modular, documented and have a lot of internal typespecs. Performance
- improvements are also expected.
- Expect noticeable performance improvements for large BYTEA / TEXT / VARCHAR / JSON / JSONB etc fields.
- Now it's possible to preserve original exception's stacktrace, finally!
- (see https:
- https:
- Incompatibilities:
- for a large result sets (when a lot of rows are returned by a query) and for large string/json/blob
- query parameters
- modules. So, some new dialyzer warnings might pop-up
- mapping table, which might be quite big in some cases. This also may produce bigger error_logger
- reports in case of epgsql connection process crashes.
- modifications were made to this code.
- deprecated (so, `epgsql:equery(C, "SELECT $1::text", [my_atom])` will still work but is not recommended)
- In 3.4.0
- In 3.3.0
- https:
- http:
- (now returns `{ok, 0, Columns, []}` instead of `{ok, 0}`)
- In 3.2.0:
- In 3.1.1:
- In 3.1.0:
- In 3.0.0:
|