public inbox for [email protected]
help / color / mirror / Atom feedFrom: Ron Johnson <[email protected]>
To: Daniel Verite <[email protected]>
Cc: Andy Hartman <[email protected]>
Cc: [email protected]
Subject: Re: Display Bytea field
Date: Fri, 10 Jan 2025 09:39:10 -0500
Message-ID: <CANzqJaDrj6mYQ0zoXL=q1aWFE117zeExYzmyqnNDHPcnaB+SVg@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <CAEZv3copeUd7mNf98qxBtkqqW=g3MtCJe62jdMEEzFC4M=-+4A@mail.gmail.com>
<[email protected]>
On Fri, Jan 10, 2025 at 7:49 AM Daniel Verite <[email protected]>
wrote:
[snip]
> 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.
>
This is what I did when migrating Oracle xLOB columns to bytea. Had to use
upper(md5()).
I didn't suggest this earlier, since I don't know the details of MSSQL's
Image data type.
--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!
view thread (2+ messages)
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected]
Subject: Re: Display Bytea field
In-Reply-To: <CANzqJaDrj6mYQ0zoXL=q1aWFE117zeExYzmyqnNDHPcnaB+SVg@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox