On Wed, Oct 23, 2019 at 10:05:44PM -0400, Bruce Momjian wrote:
> My reading of the commit message is that the error messages will just be
> more helpful now, not that some things would now error that use to be
> ignored. I am still unclear exactly what the release notes should say.
Nay. It could
PG Doc comments form writes:
> The following documentation comment has been logged on the website:
> Page: https://www.postgresql.org/docs/12/functions-json.html
> Description:
> '{"a":[1,2,3,4,5]}'::jsonb @@ '$.a[*] > 2' does not work;
> '{"a":[1,2,3,4,5]}'::jsonb @@ '$.a[*] > 2'::jsonpath work
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/12/functions-json.html
Description:
'{"a":[1,2,3,4,5]}'::jsonb @@ '$.a[*] > 2' does not work;
'{"a":[1,2,3,4,5]}'::jsonb @@ '$.a[*] > 2'::jsonpath works as expected
Hi.
This is not clear from doc, so I have asked on IRC too.
from the DOC: https://www.postgresql.org/docs/current/trigger-definition.html
In the case of INSTEAD OF triggers, the possibly-modified row returned by each
trigger becomes the input to the next trigger
I modify OLD row, thus I expect
On Thu, Oct 24, 2019 at 5:31 PM Bruce Momjian wrote:
> Uh, I am wondering if it is just too details for our docs. Can you
> think of some text and its location?
>
>
"Unique indexes on functions can be used to create special types of
constraints, like considering unique values equal (coalesce) or
On 2019-10-28 23:41, PG Doc comments form wrote:
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/12/ddl-generated-columns.html
Description:
https://www.postgresql.org/docs/12/ddl-generated-columns.html
In the below
"Consider the differe
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/12/ddl-generated-columns.html
Description:
https://www.postgresql.org/docs/12/ddl-generated-columns.html
In the below
"Consider the differences between a column with a default and a generate