From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Vincent Veyron <vv(dot)lists(at)wanadoo(dot)fr>, Dan Kortschak <dan+pgsql(at)kortschak(dot)io> |
Cc: | 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 20:35:42 |
Message-ID: | 2f11b2ba-3182-492a-ab46-23cfa5ec913c@aklaver.com |
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
> Dan Kortschak <dan+pgsql(at)kortschak(dot)io> wrote:
>
>> My question is where would be the best place for me to looks to learn
>> about how to implement a port of this SQLite? and what would broadly be
>> the most sensible approach to take (to narrow down what I need to read
>> through in learning)?
>>
>
> 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
Just know that SQLite does not enforce types, therefore it is entirely
possible that there are values in fields that are not valid in Postgres.
Think:
select ''::integer
ERROR: invalid input syntax for type integer: ""
LINE 1: select ''::integer
>
> If your query works in SQLite, all you have to do is read those, and try to port; if it fails, read them again. Also search the archives of the pgsql-general list, many answers in there
>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Dominique Devienne | 2024-07-23 21:52:47 | Re: re-novice coming back to pgsql: porting an SQLite update statement to postgres |
Previous Message | Tom Lane | 2024-07-23 20:32:27 | Re: Issue while creating index dynamically |