Kamil Listopad

Unfortunately, I cannot move forward with it until selda dependencies are added to the package-set. I plan to merge current PRs as soon as the dependencies are ready and then...

So it's nothing specific to selda, but it's still worth mentioning as this problem shows up pretty often. We can use type synonym trickery to reuse some of this structure...

Since fields that are `Auto` cannot be passed to `insert` query (because we want for the DB to generate these values `Auto`matically) it might be better to separate these fields...

@paluh if it's only removing `primPGEscape` call from `Any` then it shouldn't be problematic to apply this change for `master`. At least there's a workaround - use `litPG` for now...

Right, this is really interesting as there are two things 1. how to insert query expressions (of type `Col s a`), guide only mentions inserting non-query expressions (of type `a`)...

I see, that's very clever ;) This points out that we cannot create a query without a `FROM` clause. I've opened an issue #46 for it. Nice workaround using `Source`...

Unfortunately there's no easy way to add this variant. Customization of statements like `INSERT` is not yet possible. For now you can write your own insert operation. You'd need to...

Yes, it looks like it. Does it work for you? If you care only about postgresql then you can drop the type class `GenericInsertOnConflict` and merge the instance with `insertOnConflict_...

Types are already complex enough - complicating expression types `Col s a` is probably not worth it. Unless someone finds a real value in implementing a type-safe solution this will...

Hi @vladciobanu! Thanks for your interest! I believe what you (almost) want is already implemented on the master branch, but the problem is that we haven't yet published it. [Here](https://github.com/Kamirus/purescript-selda/blob/scope-as-backend/guide/Custom.md#new-custom-type)...