Re: Oracke BLOB to Postgres BYTEA using ora2pg - Mailing list pgsql-general

From Pavel Stehule
Subject Re: Oracke BLOB to Postgres BYTEA using ora2pg
Date
Msg-id CAFj8pRAF618pshsWQB4yYbVWjPAMpqWUMTj5U+q8Rj=jMTuCTA@mail.gmail.com
Whole thread Raw
In response to RE: Oracke BLOB to Postgres BYTEA using ora2pg  ("Daniel Verite" <daniel@manitou-mail.org>)
List pgsql-general


út 15. 1. 2019 v 12:56 odesílatel Daniel Verite <daniel@manitou-mail.org> napsal:
        Mihalidesová Jana wrote:

> nipjd=> select distinct encode(serializable_value, 'escape') from
> alf_node_properties_zaloha where serializable_value is not null;
>                                                                                                             encode
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> decode(E'aced00057e72002c6f72672e616c66726573636f2e736572766963652e636d722e76657273696f6e2e56657273696f6e5479706500000000000000001200007872000e6a6176612e6c616e672e456e756d000000000000000012000078707400054d494e4f52',
> 'hex')

These contents are code, in the form of function calls, instead of data.
Possibly if you ran these function calls they would output the
original data, but that's a pretty weird form of storage.  If the
insert was done by Ora2Pg, you want to report this as a bug.

+1


a author is very cooperative

Regards

Pavel


Best regards,
--
Daniel Vérité
PostgreSQL-powered mailer: http://www.manitou-mail.org
Twitter: @DanielVerite

pgsql-general by date:

Previous
From: Ravi Krishna
Date:
Subject: Re: Read consistency when using synchronous_commit=off
Next
From: pshadangi
Date:
Subject: Re: Read consistency when using synchronous_commit=off