| From: | Dan Kortschak <dan+pgsql(at)kortschak(dot)io> |
|---|---|
| To: | Dominique Devienne <ddevienne(at)gmail(dot)com>, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
| Cc: | Vincent Veyron <vv(dot)lists(at)wanadoo(dot)fr>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: re-novice coming back to pgsql: porting an SQLite update statement to postgres |
| Date: | 2024-07-24 00:23:00 |
| Message-ID: | 735913e4c9601a2a7ad57d2253d74451c42ba899.camel@kortschak.io |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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 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.
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Durgamahesh Manne | 2024-07-24 13:05:46 | pg_repack job scheduling with pg_cron |
| Previous Message | Dominique Devienne | 2024-07-23 21:52:47 | Re: re-novice coming back to pgsql: porting an SQLite update statement to postgres |