Replace the bind method with named parameter

[NicklasWallgren]

It might be a good idea to replace the current {{bind .Id}} method with typical named parameters e.g. :id.

sqlx supports it https://github.com/jmoiron/sqlx/blob/a62bc6088664eb854c3d5ebbd08a1ffd59662ef1/named.go#L331

It would probably increase the memory usage as well as cpu utilization, but it might be worth with.

[pivaldi]

If this this pull request is accepted, it will be easy to add any bindings engine as named placeholder.

[pivaldi]

Having thought about it, I wonder what would be the point of making a binding when it would be enough to write down the named parameter yourself…
What is the gain to write {{bind .Id}} to obtain :id instead of directly write :id in the template ? 🤔

[NicklasWallgren]

What is the gain to write {{bind .Id}} to obtain :id instead of directly write :id in the template ? 🤔

You don't know beforehand which query params are to be expected, due to potential if-statements/conditionals in the template. We cannot deduce which query parameters the generated query expects without the bind method.

[pivaldi]

OK, I understand, you expect a universal binding engine.

I don't think the actual bind engine should be replaced by a named bind because this will introduce a strong dependency with sqlx or other ORM-like.
Maybe an other type of binding ? nbind (for named bind)

Note that it will be impossible that {{nbind .Id}} gives :id because .Id is the value, not the field name…
Or use regexp replace, which will not be as reliable as default template parsing.

Why the binding engine will not replace {{nbind .Id}} by his own named binding :UNIQ_HASH and GetParams will return the corresponding map[string]any usable with sqlx ?