diff options
| author | Peter Eisentraut <peter@eisentraut.org> | 2025-11-21 17:36:25 +0100 |
|---|---|---|
| committer | Peter Eisentraut <peter@eisentraut.org> | 2025-11-21 17:36:25 +0100 |
| commit | 51364113d5a00e53f9447de1f7056c440e0892d5 (patch) | |
| tree | 5811294cbaff91479b91ae0196b403a6314ece0f | |
| parent | ef8fe693606add7edb563e6c8a63c6ef608338c0 (diff) | |
Fix typo in documentation about application time
Author: Paul A. Jungwirth <pj@illuminatedcomputing.com>
| -rw-r--r-- | doc/src/sgml/ddl.sgml | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/doc/src/sgml/ddl.sgml b/doc/src/sgml/ddl.sgml index bf574a1741b..09ad8400fd0 100644 --- a/doc/src/sgml/ddl.sgml +++ b/doc/src/sgml/ddl.sgml @@ -1610,7 +1610,7 @@ CREATE TABLE circles ( <para> <firstterm>Application time</firstterm> refers to a history of the entity - described by a table. In a typical non-temporal table, there is single + described by a table. In a typical non-temporal table, there is a single row for each entity. In a temporal table, an entity may have multiple rows, as long as those rows describe non-overlapping periods from its history. Application time requires each row to have a start and end time, @@ -1806,7 +1806,6 @@ CREATE TABLE variants ( </figure> <para> - In a table, these records would be: <programlisting> id | product_no | name | valid_at |
