Ok, we checked our client code to eliminate this problem. Thanks for the doc patch.<br /><br /> Regards,<br /><br />
Dirk<br/><br /> Simon Riggs wrote: <blockquote cite="mid1152534578.2518.32.camel@localhost.localdomain"
type="cite"><prewrap="">On Mon, 2006-07-10 at 13:35 +0200, Dirk Lutzebäck wrote:
</pre><blockquote type="cite"><pre wrap="">In any case I would see this as a security problem because you cannot
control sql code injection easily (as with using DBD::Pg) if you have
to pass parameters in the SQL string to use partial indexes. </pre></blockquote><pre wrap="">
That's not what I said. I see no security problem as a result of this
behaviour.
</pre></blockquote><br /><div class="moz-signature">-- <br /><small><i>This email and any files transmitted with it
areconfidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not
theintended recipient, you should not copy it, re-transmit it, use it or disclose its contents, but should return it to
thesender immediately and delete your copy from your system. Thank you for your cooperation.</i></small><p><b>Dirk
Lutzebäck</b><a class="moz-txt-link-rfc2396E" href="mailto:lutzeb@aeccom.com"><lutzeb@aeccom.com></a> Tel
+49.30.5362.1635Fax .1638<br /> CTO <a href="http://www.aeccom.com">AEC/communications GmbH</a>, Berlin, Germany </div>