[new release] pgx_lwt_mirage, pgx_value_core, pgx_async, pgx_unix, pgx_lwt_unix, pgx_lwt and pgx (2.0) #18675
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pgx using Lwt on Mirage for IO
CHANGES:
Breaking changes
Pgx_aux
,Types
,Access
, etc. aren't added to the global scope.The main result of this is that
Pgx_value
now needs to be accessed asPgx.Value
.(Set Pgx module to wrapped arenadotio/pgx#103)
Pgx_async.connect
andwith_conn
now have an additional optional?ssl
argument (see below).Added
new
?ssl
argument toconnect
andwith_conn
.(Add TLS support for Pgx_async arenadotio/pgx#108)
Fixed
Pgx_eof
, and now they raisePostgreSQL_Error("Failed to authenticate with postgres server", additional details ...)
.(improve message for authentication errors arenadotio/pgx#105)
Changed