On Mon, Aug 5, 2024 at 5:01 PM Tom Lane wrote:
>
> Dominique Devienne writes:
> > The reason I find the restriction damaging is that `FROM t1, t2 WHERE
> > t1.c1 = t2.c2`
> > is the "old" way to write joins, versus the "newer" `FROM t1 JOIN t2
> > ON t1.c1 = t2.c2`
> > which IMHO better separates
Dominique Devienne writes:
> The reason I find the restriction damaging is that `FROM t1, t2 WHERE
> t1.c1 = t2.c2`
> is the "old" way to write joins, versus the "newer" `FROM t1 JOIN t2
> ON t1.c1 = t2.c2`
> which IMHO better separates "filtering" from "joining" columns. FWIW.
But the whole poin
On Mon, Aug 5, 2024 at 7:36 AM Dominique Devienne
wrote:
> I'd rather SQLite and PostgreSQL continue to agree on this,
> but not in a restrictive way.
I.e., you want to support the SQL Server syntax; allow the table named in
UPDATE to be repeated, without an alias, in which case it is taken to
On Mon, Aug 5, 2024 at 3:56 PM Tom Lane wrote:
> Dominique Devienne writes:
> > In https://sqlite.org/forum/forumpost/df23d80682
> > Richard Hipp (Mr SQLite) shows an example of something
> > that used to be supported by SQLite, but then wasn't, to be
> > compatible with PostgreSQL.
> This seems
Dominique Devienne writes:
> In https://sqlite.org/forum/forumpost/df23d80682
> Richard Hipp (Mr SQLite) shows an example of something
> that used to be supported by SQLite, but then wasn't, to be
> compatible with PostgreSQL.
For the archives' sake:
CREATE TABLE t1(aa INT, bb INT);
CREATE TABLE
On Monday, August 5, 2024, Dominique Devienne wrote:
> In https://sqlite.org/forum/forumpost/df23d80682
> Richard Hipp (Mr SQLite) shows an example of something
> that used to be supported by SQLite, but then wasn't, to be
> compatible with PostgreSQL.
>
> Thus I'm curious as to why PostgreSQL re
