> -----Original Message-----
> From: Dan Langille [mailto:dan@langille.org]
> Sent: 23 June 2003 14:45
> To: Dave Page
> Cc: pgadmin-support@postgresql.org
> Subject: RE: [pgadmin-support] Migration wizard cannot
> connect via ODBC
>
>
> 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)
That's almost certainly the problem then. pgAdmin (or more precisely VB)
is barfing on the control character (which mysqldump nicely outputs as a
charcode).
Not much I can do about that I'm afraid.
Regards, Dave.
