From ebe124eacd7c3faa36ed358e7cc1d7c5b419e5f6 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Sat, 4 May 2024 14:18:09 +0200 Subject: Merging upstream version 15.6. Signed-off-by: Daniel Baumann --- doc/src/sgml/html/rules-views.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'doc/src/sgml/html/rules-views.html') diff --git a/doc/src/sgml/html/rules-views.html b/doc/src/sgml/html/rules-views.html index 41bb926..a49c074 100644 --- a/doc/src/sgml/html/rules-views.html +++ b/doc/src/sgml/html/rules-views.html @@ -1,5 +1,5 @@ -41.2. Views and the Rule System
41.2. Views and the Rule System
Prev UpChapter 41. The Rule SystemHome Next

41.2. Views and the Rule System

41.2.1. How SELECT Rules Work
41.2.2. View Rules in Non-SELECT Statements
41.2.3. The Power of Views in PostgreSQL
41.2.4. Updating a View

+41.2. Views and the Rule System

41.2. Views and the Rule System
Prev UpChapter 41. The Rule SystemHome Next

41.2. Views and the Rule System

41.2.1. How SELECT Rules Work
41.2.2. View Rules in Non-SELECT Statements
41.2.3. The Power of Views in PostgreSQL
41.2.4. Updating a View

Views in PostgreSQL are implemented using the rule system. In fact, there is essentially no difference between: @@ -503,4 +503,4 @@ SELECT t1.a, t2.b, t1.ctid FROM t1, t2 WHERE t1.a = t2.a; triggers for the view, and the rewriter cannot automatically rewrite the query as an update on the underlying base relation, an error will be thrown because the executor cannot update a view as such. -

Prev Up Next
41.1. The Query Tree Home 41.3. Materialized Views
\ No newline at end of file +

Prev Up Next
41.1. The Query Tree Home 41.3. Materialized Views
\ No newline at end of file -- cgit v1.2.3