Hi

Thanks for the report. Do you have the same issue with BLOB ?

from ora2pg.

Fixed for RAW datatype in commit 199a4b5, please use latest code from github. Normally BLOB should not have the same issue because they are not returned as HEX string. Let us know if you have any other problem with that.

Regards,

from ora2pg.

Hi,
I had tested this with a raw column only (no BLOB).

Best regards
Jens

From: Darold [mailto:[email protected]]
Sent: Mittwoch, 26. Februar 2014 10:34
To: darold/ora2pg
Cc: Jens Wiechmann
Subject: Re: [ora2pg] missing escapes for bytea columns (#52)

Hi

Thanks for the report. Do you have the same issue with BLOB ?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/52#issuecomment-36106811.

from ora2pg.

Hi,
thanks for the quick response.
Here is the result of the latest sources from the github:
-- Generated by Ora2Pg, the Oracle database Schema converter, version 12.1
:
SET client_encoding TO 'LATIN1';
\set ON_ERROR_STOP ON

BEGIN;
TRUNCATE TABLE tt;

COPY tt (c) FROM STDIN;
\xABBAFF
.

COMMIT;

But a second backslash is missing. I see \x but not \x
The wrong result is this:

select * from tt;

  c       

\xab42414646
(1 row)
Only the first two byte are correct.

from ora2pg.

Right, fixed in commit d4b1c8c

from ora2pg.

It works now. Thank you.

from ora2pg.