------- You are receiving this mail because: ------- You are the QA contact for the bug.
http://bugs.exim.org/show_bug.cgi?id=508 --- Comment #8 from Jeremy Harris <[email protected]> 2015-01-18 14:13:23 --- We don't support the parameterized interface to pgsql. Doing so would be a separate job, and not back-compatible (we'd need to support both). It would have the advantage that quoting is not required for parameters. Is it ever required for the command, and if so does it depend on the DB encoding? On the quoting issue: the pgsql docs (eg. http://www.postgresql.org/docs/8.4/static/libpq-exec.html section 30.3.4) does say that the quoting required may change with the encoding; hence the recommended interface is tied to a connection, and the alternate that is not should not be used for a client program that uses multiple connections (so we cannot). The problem for exim is that quoting is almost certainly needed before the relevant connection is made, given the current handling of them and expansion processing. We could potentially take a complete connection-spec (including encoding) supplied with the quote operator, and match connections the same way the lookup does. Undecorated quote expansions would use the default connection/s set by pgsql_servers. -- Configure bugmail: http://bugs.exim.org/userprefs.cgi?tab=email -- ## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##
