Kamil Listopad
Kamil Listopad
Right now `insert` (`insert_`) executes a query for each given record, then it concatenates the result. It should insert all of them with just one query.
`orderBy c1` in a query without `groupBy c1` and `c1` not used in an aggregate function results in a runtime error.
```purescript selectFrom_ (selectFrom table \{ id } → do -- missing `aggregate $` before selectFrom pid ← groupBy id pure { pid }) pure ``` results in an unclear error...
Right now only the test suite with queries is shared, but recreating tables and common inserts, deletes and updates could be shared too.
Add literate ps cookbook guide with a table of contents on the top of the file Write about: - Custom Types (PG) - litPG - EForeign - ShowM for custom...
Make it possible to run only certain test suites, e.g. only PG or only SQLite3 potentially useful lib: [optparse](https://github.com/f-o-a-m/purescript-optparse)
Write an introductory guide explaining what selda can do, how to write some queries and how to use it in a real-life application.
It would be nice to have generated SQL next to the test cases or pretty-printing it during test execution. It needs discussion.
The problem is with functions like [`withTransaction`](https://github.com/rightfold/purescript-postgresql-client/blob/680da31ee1c6430fe296788994fe029024c75ade/src/Database/PostgreSQL/PG.purs#L53) or `withConnection` that require a function `(m a -> Aff (Either PGError a))`, where `m` is the constrained monad. AFAIK you must concretize...