Consider using named parameters in queries

[vrom911]

We can use postgresql-simple-named library for this.

[rashadg1030]

@vrom911 This is really cool. I agree we should introduce this.

[rashadg1030]

I was trying to look for an example, but can this be used with executeMany?

[chshersh]

@rashadg1030 We don't have executeMany implemented in postgresql-simple-named library... I've created an issue about that:

• Implement executeManyNamed Holmusk/postgresql-simple-named#15

But you still can use named parameters in other functions that don't use executeMany.

[chshersh]

I think that this issue is also unblocked. We can start using named parameters right now to avoid migration to this way later when there are more functions to refactor. So every SQL query that is not used under executeMany can be moved to use queryNamed or executeNamed. You can check three-layer to see how to perform this migration (it's not straightforward because you need to deal with MonadError parametrised by different types but possible).

• https://github.com/Holmusk/three-layer/blob/1b58ec102f206681b66a584ca4a7d18f2eb4ef81/src/Lib/Db/Functions.hs#L59-L67