Re: re-novice coming back to pgsql: porting an SQLite update statement to postgres

From: Dominique Devienne <ddevienne(at)gmail(dot)com>
To: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
Cc: Vincent Veyron <vv(dot)lists(at)wanadoo(dot)fr>, Dan Kortschak <dan+pgsql(at)kortschak(dot)io>, pgsql-general(at)postgresql(dot)org
Subject: Re: re-novice coming back to pgsql: porting an SQLite update statement to postgres
Date: 2024-07-23 21:52:47
Message-ID: CAFCRh-8d-gsERdu-6W2fb0d6HLi8_bPkS7zVqm0J4ZakpvJQYw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, Jul 23, 2024 at 10:35 PM Adrian Klaver
<adrian(dot)klaver(at)aklaver(dot)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)='blob') for example.

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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Dan Kortschak 2024-07-24 00:23:00 Re: re-novice coming back to pgsql: porting an SQLite update statement to postgres
Previous Message Adrian Klaver 2024-07-23 20:35:42 Re: re-novice coming back to pgsql: porting an SQLite update statement to postgres