>Le 25/09/2010 01:09, Dave Page a écrit :
>> On Fri, Sep 24, 2010 at 11:54 PM, Guillaume Lelarge
>> <guillaume@lelarge.info> wrote:
>>
>>> Much better. So, the only way to fix this, AFAICT, is to set bytea_ouput
>>> to "escape" when connected to a 9.0 server. My question is this: should
>>> I set the parameter at the connection start, or should I set and unset
>>> it during the search of triggers? The latter is less error prone, but
>>> requires to execute three more queries (SHOW bytea_output, SET
>>> bytea_output TO escape, SET bytea_output TO old_value).
>>
>> Please set at connection. The old output is what all the rest of the
>> code expects (if anywhere does expect it), so I can't imagine it would
>> break anything.
>>
>
>OK, that was also my favorite solution. Just pushed my commits on 1.12
>and master.
>
Guillaume,
Thank you for the quick fix!
Christopher A Hotchkiss
JPMorgan Chase & Co.
Email christopher.a.hotchkiss@jpmchase.com
This communication is for informational purposes only. It is not
intended as an offer or solicitation for the purchase or sale of
any financial instrument or as an official confirmation of any
transaction. All market prices, data and other information are not
warranted as to completeness or accuracy and are subject to change
without notice. Any comments or statements made herein do not
necessarily reflect those of JPMorgan Chase & Co., its subsidiaries
and affiliates.
This transmission may contain information that is privileged,
confidential, legally privileged, and/or exempt from disclosure
under applicable law. If you are not the intended recipient, you
are hereby notified that any disclosure, copying, distribution, or
use of the information contained herein (including any reliance
thereon) is STRICTLY PROHIBITED. Although this transmission and any
attachments are believed to be free of any virus or other defect
that might affect any computer system into which it is received and
opened, it is the responsibility of the recipient to ensure that it
is virus free and no responsibility is accepted by JPMorgan Chase &
Co., its subsidiaries and affiliates, as applicable, for any loss
or damage arising in any way from its use. If you received this
transmission in error, please immediately contact the sender and
destroy the material in its entirety, whether in electronic or hard
copy format. Thank you.
Please refer to http://www.jpmorgan.com/pages/disclosures for
disclosures relating to European legal entities.
