MIME-Version: 1.0
References: <1aea530e4c96109b91fdde53a29e38beb625dc77.camel@kortschak.io>
 <20240723221121.51f2b3872d0ebfc36a6fa8ff@wanadoo.fr> <2f11b2ba-3182-492a-ab46-23cfa5ec913c@aklaver.com>
In-Reply-To: <2f11b2ba-3182-492a-ab46-23cfa5ec913c@aklaver.com>
From: Dominique Devienne <ddevienne@gmail.com>
Date: Tue, 23 Jul 2024 23:52:47 +0200
Message-ID: <CAFCRh-8d-gsERdu-6W2fb0d6HLi8_bPkS7zVqm0J4ZakpvJQYw@mail.gmail.com>
Subject: Re: re-novice coming back to pgsql: porting an SQLite update
 statement to postgres
To: Adrian Klaver <adrian.klaver@aklaver.com>
Cc: Vincent Veyron <vv.lists@wanadoo.fr>, Dan Kortschak <dan+pgsql@kortschak.io>, 
	pgsql-general@postgresql.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://www.postgresql.org/message-id/CAFCRh-8d-gsERdu-6W2fb0d6HLi8_bPkS7zVqm0J4ZakpvJQYw%40mail.gmail.com>
Precedence: bulk

On Tue, Jul 23, 2024 at 10:35=E2=80=AFPM Adrian Klaver
<adrian.klaver@aklaver.com> wrote:
> Just know that SQLite does not enforce types [...]

That's true, and applies to the OP's schema.

But for the record, SQLite *can* enforce types these days,
on an opt-in basis, with [STRICT tables][1].
Albeit with a limited type-system. --DD

PS: and could be done manually even before, with CHECK
(typeof(col)=3D'blob') for example.

[1]: https://www.sqlite.org/stricttables.html