From: | "Dan Langille" <dan(at)langille(dot)org> |
---|---|
To: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
Cc: | <pgadmin-support(at)postgresql(dot)org> |
Subject: | Re: Migration wizard cannot connect via ODBC |
Date: | 2003-06-23 13:45:14 |
Message-ID: | 3EF6CC2A.10127.346BB8BE@localhost |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
On 23 Jun 2003 at 14:35, Dave Page wrote:
> > 23/06/2003 9:04:58 AM - SQL (phorum_conversion): INSERT INTO
> > "newforum1_bodies" ("id", "body", "thread") VALUES ('151',
> > '<HTML>Uh, Internal Server Errors may be triggered by a
> > particular browser, but the problem _lies on the server
> > itself_, so you''d best off scouring your error logs for
> > clues.</HTML>', '133')
> > 23/06/2003 9:04:58 AM - SQL (phorum_conversion): INSERT INTO
> > "newforum1_bodies" ("id", "body", "thread") VALUES ('155',
> > '<HTML>tr -d "
> > 23/06/2003 9:04:58 AM - SQL (phorum_conversion): ROLLBACK
>
> I notice that the query is not even fully built - could there be a \0 or
> some other odd character in your data? A non-escaped quote or wahtever
> wouldn't prevent the SQL being built in this way - it would just be
> invalid SQL.
Looking at the output of mysqldump, I found this:
(155,'<HTML>tr -d \"\015\" < dosfile.txt\r\n</HTML>',155)
--
Dan Langille : http://www.langille.org/
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2003-06-23 14:00:09 | Re: Migration wizard cannot connect via ODBC |
Previous Message | Dave Page | 2003-06-23 13:35:44 | Re: Migration wizard cannot connect via ODBC |