rdbc-io / rdbc-pgsql Goto Github PK

Decide whether returning DB values should always be in binary format, if so, make appropriate changes to PgParametrizedStatement.

Use binary parameters at first attempt and textual as a fallback. Investigate whether PG supports textual for all possible datatypes. Make it possible for a pg type converter to implement only textual or only binary format

Fix TODO, don't fill config props, this should be the other way around

This issue is only about not crashing on unknown NotificationResponse backend message, not about Postgres' LISTEN/NOTIFY mechanism support.

Investigate the code whether it really is non-blocking and possibly fix it.

Generally clean up all the code, deal with code duplication, too long methods etc.

PgTypeConv has to be aware of DB settings (StatusParameter) see TimestampTypeConv for example, it needs info about data format I think

validate method now returns IllegalSessionStateException if connection is already closed. It should return ConnectionValidationException in this case. It should still return IllegalSessionStateException if connection is in use though

Akka stream is quite a big dependency and the library is not using many features of it. Consider dropping this dependency.

unknown and unhandled msgs have to be handled inside fsm to complete a promise that client's waiting on

DescribedDataRow is not needed, see how extended querying makes queries without described data row. DescribedDataRow shouldn't be used for simple queries.

Insert doesnt implement Statement where deallocate method is. This should change I think. Insert should also have streamParams method.

Allow setting SQL null values as Nones and not null SQL values as Somes.

In non-select operations like non-returning inserts, deletes, updates there are many optimizations available:

• don't set up a publisher (stream)
• don't do describe, do parse & bind & execute together
• something else?