Hello.
What do you think about switching to mysqldump with --hex-blob
option?
"[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
> Restoring a backup of a very large database, I've received an error
> message by the server (4.13) about an sql syntax error. I've done the
> backup with mysql administrator and I've used the same procedure for
> months without problems.
> I've discovered that problem is into a blob
> field that store long descriptive text. That filed, is populated
> automatically with an import procedure from an Oracle db where, when a
> phrase is too long, it continues on another record. In this field,
> often is stored phrases contained between quotation marks ("). However
> the problem is present only when the phrase begin into a record with
> quotation marks and reach the end into the next record BUT with the
> ONLY quotation marks.
> How can I solve this problem if I cannot modify
> the insert sql statement? I need an expedient that works only for the
> backup and restore procedures.
> Thanks a lot
> Stefano
>
--
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sponsored by Ensita.NET http://www.ensita.net/
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Gleb Paharenko
/ /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED]
/_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET
<___/ www.mysql.com
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
