On Mon, Aug 5, 2024 at 8:50 PM Sandeep Thakkar
wrote:
> This issue is seen only on v16 and not the back branches (tested on 15 and
> 14) and also confirmed by @Ertan Küçükoglu at
> https://github.com/EnterpriseDB/edb-installers/issues/127#issuecomment-2268371442
Does that mean you can reproduce
to quote the documentation:
> If an unquoted colon (:) followed by a psql variable name appears within
an argument, it is replaced by the variable's value, as described in SQL
Interpolation below.
> The forms :'variable_name' and :"variable_name" described there work as
well. The :{?variable_name}
Hi!
I want to check if I pass the parameter "param1" to a sql script
"delme.sql" like
```
\if ':param1'
\echo :param1;
\else
\prompt 'Param1? ' :param1
\endif
select :'param1';
```
if parameter `param1` is not passed, the .sql should ask for it.
If I run something like
`psql -f delme.sql -v pa
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
On Mon, 5 Aug 2024 at 23:41, Dominique Devienne wrote:
> Is that now required? Any documentation / release notes regarding
> such a change?
Yes. The release notes mention:
"Remove the Microsoft Visual Studio-specific PostgreSQL build option
(Michael Paquier)
Meson is now the only available met
Hi. I'm using as the go-between for a colleague that's not subscribed
to this ML.
In short, we have Python-based automation scripts to build our 3rd parties.
And the ones we have, that worked fine with v16, do not with v17
beta2, on Windows.
Thus I'm asking for advice as how we should proceed. TIA
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 refuses the first formulation.
Could anyone provide any insights? Th
Hi Thomas,
This issue is seen only on v16 and not the back branches (tested on 15 and
14) and also confirmed by @Ertan Küçükoglu at
https://github.com/EnterpriseDB/edb-installers/issues/127#issuecomment-2268371442
On Fri, Aug 2, 2024 at 6:14 PM Sandeep Thakkar <
sandeep.thak...@enterprisedb.co
13 matches
Mail list logo
