Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sWPmi-00F2h5-UB for pgsql-general@arkaria.postgresql.org; Wed, 24 Jul 2024 00:23:13 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sWPmg-00HUVH-JO for pgsql-general@arkaria.postgresql.org; Wed, 24 Jul 2024 00:23:11 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sWPmf-00HUV9-TR for pgsql-general@lists.postgresql.org; Wed, 24 Jul 2024 00:23:10 +0000 Received: from mail-4317.proton.ch ([185.70.43.17]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sWPmc-0018ct-NH for pgsql-general@postgresql.org; Wed, 24 Jul 2024 00:23:09 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kortschak.io; s=protonmail3; t=1721780585; x=1722039785; bh=LNeu3KgR58A9R+ydtxXghERozU5Ye2uaZCGQeouXtlc=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector; b=0uTklZ2QoETIMh17gnKrzJcNncOuV1aCfzYL5n9bIkiw5oazEL5uGqS21xqaZ3rNJ mk+/PqATpFkUxXcaqHGhlUYeh5vM5kAOx6UOLUjDjm7rYYWN+2UZQwQ2Zq4EcvYujX RLhZJdO7KPYsFhup4IyCkMqUW4ZuSyhxZ2H/fwhY2yUg26JccN1brL70UnoWh2OFWE 0r7aparcl+J1Nhf63V7OHm3Rvy/0CcAVBqi3HnLJs6E/oOR8eOfG/LhfiiLmRFL55/ PJ/dQZgjW8QFOsW/1jDEUf2CxNgFktTse/VcRUWijEYodw1J3nw/mQcn2jIc64iXrd Vj4M8J5DvW2bg== Date: Wed, 24 Jul 2024 00:23:00 +0000 To: Dominique Devienne , Adrian Klaver From: Dan Kortschak Cc: Vincent Veyron , pgsql-general@postgresql.org Subject: Re: re-novice coming back to pgsql: porting an SQLite update statement to postgres Message-ID: <735913e4c9601a2a7ad57d2253d74451c42ba899.camel@kortschak.io> In-Reply-To: References: <1aea530e4c96109b91fdde53a29e38beb625dc77.camel@kortschak.io> <20240723221121.51f2b3872d0ebfc36a6fa8ff@wanadoo.fr> <2f11b2ba-3182-492a-ab46-23cfa5ec913c@aklaver.com> Feedback-ID: 18519778:user:proton X-Pm-Message-ID: ed6c60220ff8c2b6e8839b3ba0ea1f1054bd3284 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 7/23/24 13:11, Vincent Veyron wrote: > On Mon, 15 Jul 2024 20:31:13 +0000 > > This is the goto page for anything SQL : > https://www.postgresql.org/docs/current/sql-commands.html > > For DateTime types : > https://www.postgresql.org/docs/current/datatype-datetime.html > > For JSON types : > https://www.postgresql.org/docs/current/datatype-json.html Thanks, I will work through those. On Tue, 2024-07-23 at 23:52 +0200, Dominique Devienne wrote: > On Tue, Jul 23, 2024 at 10:35=E2=80=AFPM Adrian Klaver > wrote: > > Just know that SQLite does not enforce types [...] >=20 > That's true, and applies to the OP's schema. Thank you both. Yes, I was aware of this weirdness of the schema (I inherited it) and was shocked that it worked when I relaised. I'll be happier when types are properly enforced, but I don't think I can retrospectively enforce that on the SQLite implementation I have.