pgo
pgo copied to clipboard
erleans
Erlang Postgres client and connection pool
The pool name is used to [register](https://github.com/erleans/pgo/blob/main/src/pgo.erl#L97) the pid and [find](https://github.com/erleans/pgo/blob/main/src/pgo_pool.erl#L321) it: ``` gen_server:start_link({local, Pool}, ?MODULE, {Pool, PoolConfig1}, []). erlang:whereis(Pool) ``` Having a default pool name is useful but isn't...
This gives an error: ```erlang pgo:query(>, [{{2020, 2, 1}, {0, 0, 0}}]). {error,function_clause} ``` Casting to timestamptz works: ```erlang pgo:query(>, [{{2020, 2, 1}, {0, 0, 0}}]). #{command => select,num_rows =>...
The purpose of the optional DB Connector is to have a standard interface for the rest of the app to communicate with PGO. This will make it easy to reflect...
- The `pool_options` field is missing in the `options()` type. - `timeout` is a valid `pool_option()`, see https://github.com/erleans/pgo/blob/master/src/pgo.erl#L95.
Would you accept a PR that allows the password to be a zero-arity function? There are a few use cases for it. One example is pulling the password from a...
Is it possible to get the field information when no matching rows are returned. For example, selecting an empty table and providing the decode fun? `decode_fun/2` provides a nice opportunity...
A sample of the possible reasons a query with PGO might fail. ``` "null value in column \"thread_id\" violates not-null constraint" "column \"zz\" does not exist" "relation \"moo\" does not...
In place of specifying user/password/host/port/db it would be great if you could pass in url as an argument to `pgo:start_pool` and `pgo_pool:start_link` Not sure if database_url or just url is...
tstzrange in PostgreSQL: ```pgsql tstzrange('2019-12-01 00:00:00+00','2019-12-02 00:00:00+00','[)') ``` In pgo: ```erlang {{{{2019,12,1},{0,0,0}},{{2019,12,2},{0,0,0}}},{true,false}} ``` Is it possible to remove one pair of parentheses to make the representation closer to PostgreSQL? ```erlang...
Accidentally set a map with a field value of `{ok, 12345}` instead of `12345`. Calling `pgo:query/2` with the param list returns only `{error, badarg}`, which is correct but challenging to...