Error handling ideas

v4-experimental
Jack Christensen 2018-11-17 20:27:20 -06:00
parent 21656fbd17
commit d41376dfbc
1 changed files with 1 additions and 0 deletions

1
v4.md
View File

@ -20,6 +20,7 @@ Potential Changes:
* Change prepared statement usage from using name as SQL text to specifically calling prepared statement (more like database/sql).
* Remove stdlib hack for RegisterDriverConfig now that database/sql supports better way
* Consider how to simplify context.Context and query cancellation support (or even remove). This logic is very complex and error prone. Perhaps connections should simply be killed on a cancelled context rather than trying to recover. Separating PostgreSQL query cancellation from context might simplify them both. Also consider that PG queries can be cancelled and connections can be terminated via SQL functions from another connection.
* Better error handling. Consider package functions that interrogate errors rather comparing to value or type. Like net.Error interface but with addition of package functions that unwrap and interrogate the error.
Minor Potential Changes: