Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: Display Bytea field
From: "Daniel Verite" <daniel@manitou-mail.org>
To: "Andy Hartman" <hartman60home@gmail.com>
Cc: pgsql-general@lists.postgresql.org
In-Reply-To: <CAEZv3copeUd7mNf98qxBtkqqW=g3MtCJe62jdMEEzFC4M=-+4A@mail.gmail.com>
Date: Fri, 10 Jan 2025 13:49:40 +0100
Message-Id: <1309d698-fa5f-493e-809a-fd6d95d913b6@manitou-mail.org>
Archived-At: <https://www.postgresql.org/message-id/1309d698-fa5f-493e-809a-fd6d95d913b6%40manitou-mail.org>
Precedence: bulk

	Andy Hartman wrote:

> How thru a simple query can I make sure data matches and I can display it
>=20
> On Thu, Jan 9, 2025 at 3:16=E2=80=AFPM Andy Hartman <hartman60home@gmail.=
com> wrote:
>=20
> > I have migrated over a Table from Mssql that had an Image column I now
> > have it in Postgres

Within psql, the bytea field can be copied into a large object
with lo_from_bytea() [1], and then the large object exported
into a local file with \lo_export [2]

Alternatively, you could compare image checksums before and
after moving them into postgres. The advantage is that you
don't need to export or view any file, and you compare globally
all your images. If the checksums are identical, the data are identical.
On the MSSQL side, checksums can be computed with hashbytes()
as suggested in this stackoverflow answer: [3]
On the postgres side, use functions like md5() or sha256()
directly on the bytea column.


[1] https://www.postgresql.org/docs/current/lo-funcs.html

[2]
https://www.postgresql.org/docs/current/app-psql.html#APP-PSQL-META-COMMAND=
-LO-EXPORT

[3] https://stackoverflow.com/a/33256990/


Best regards,
--=20
Daniel V=C3=A9rit=C3=A9
https://postgresql.verite.pro/
Twitter: @DanielVerite