From e9bff2c1bdb5c53ca24ceabcb51741735cb4043c Mon Sep 17 00:00:00 2001
From: "dependabot[bot]" <49699333+dependabot[bot]@users.noreply.github.com>
Date: Sun, 17 Mar 2024 15:57:53 +0100
Subject: [PATCH 01/22] Bump follow-redirects from 1.15.4 to 1.15.6 in /website
 (#89)

Bumps [follow-redirects](https://github.com/follow-redirects/follow-redirects) from 1.15.4 to 1.15.6.
- [Release notes](https://github.com/follow-redirects/follow-redirects/releases)
- [Commits](https://github.com/follow-redirects/follow-redirects/compare/v1.15.4...v1.15.6)

---
updated-dependencies:
- dependency-name: follow-redirects
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
---
 website/yarn.lock | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/website/yarn.lock b/website/yarn.lock
index a600871..b3112d1 100644
--- a/website/yarn.lock
+++ b/website/yarn.lock
@@ -4062,9 +4062,9 @@ flux@^4.0.1:
     fbjs "^3.0.1"
 
 follow-redirects@^1.0.0, follow-redirects@^1.14.7:
-  version "1.15.4"
-  resolved "https://registry.yarnpkg.com/follow-redirects/-/follow-redirects-1.15.4.tgz#cdc7d308bf6493126b17ea2191ea0ccf3e535adf"
-  integrity sha512-Cr4D/5wlrb0z9dgERpUL3LrmPKVDsETIJhaCMeDfuFYcqa5bldGV6wBsAN6X/vxlXQtFBMrXdXxdL8CbDTGniw==
+  version "1.15.6"
+  resolved "https://registry.yarnpkg.com/follow-redirects/-/follow-redirects-1.15.6.tgz#7f815c0cda4249c74ff09e95ef97c23b5fd0399b"
+  integrity sha512-wWN62YITEaOpSK584EZXJafH1AGpO8RVgElfkuXbTOrPX4fIfOyEpW/CsiNd8JdYrAoOvafRTOEnvsO++qCqFA==
 
 fork-ts-checker-webpack-plugin@^6.5.0:
   version "6.5.3"

From a6e1a019ee1569d6cc533d60c093eb73a34a8a24 Mon Sep 17 00:00:00 2001
From: "dependabot[bot]" <49699333+dependabot[bot]@users.noreply.github.com>
Date: Sun, 24 Mar 2024 12:09:26 +0100
Subject: [PATCH 02/22] Bump webpack-dev-middleware from 5.3.3 to 5.3.4 in
 /website (#90)

Bumps [webpack-dev-middleware](https://github.com/webpack/webpack-dev-middleware) from 5.3.3 to 5.3.4.
- [Release notes](https://github.com/webpack/webpack-dev-middleware/releases)
- [Changelog](https://github.com/webpack/webpack-dev-middleware/blob/v5.3.4/CHANGELOG.md)
- [Commits](https://github.com/webpack/webpack-dev-middleware/compare/v5.3.3...v5.3.4)

---
updated-dependencies:
- dependency-name: webpack-dev-middleware
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
---
 website/yarn.lock | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/website/yarn.lock b/website/yarn.lock
index b3112d1..7986048 100644
--- a/website/yarn.lock
+++ b/website/yarn.lock
@@ -7935,9 +7935,9 @@ webpack-bundle-analyzer@^4.5.0:
     ws "^7.3.1"
 
 webpack-dev-middleware@^5.3.1:
-  version "5.3.3"
-  resolved "https://registry.yarnpkg.com/webpack-dev-middleware/-/webpack-dev-middleware-5.3.3.tgz#efae67c2793908e7311f1d9b06f2a08dcc97e51f"
-  integrity sha512-hj5CYrY0bZLB+eTO+x/j67Pkrquiy7kWepMHmUMoPsmcUaeEnQJqFzHJOyxgWlq746/wUuA64p9ta34Kyb01pA==
+  version "5.3.4"
+  resolved "https://registry.yarnpkg.com/webpack-dev-middleware/-/webpack-dev-middleware-5.3.4.tgz#eb7b39281cbce10e104eb2b8bf2b63fce49a3517"
+  integrity sha512-BVdTqhhs+0IfoeAf7EoH5WE+exCmqGerHfDM0IL096Px60Tq2Mn9MAbnaGUe6HiMa41KMCYF19gyzZmBcq/o4Q==
   dependencies:
     colorette "^2.0.10"
     memfs "^3.4.3"

From 6d825278ec7bc205cbb466b2f11e4a0223a1cb58 Mon Sep 17 00:00:00 2001
From: "dependabot[bot]" <49699333+dependabot[bot]@users.noreply.github.com>
Date: Fri, 29 Mar 2024 08:24:13 +0100
Subject: [PATCH 03/22] Bump express from 4.18.2 to 4.19.2 in /website (#91)

Bumps [express](https://github.com/expressjs/express) from 4.18.2 to 4.19.2.
- [Release notes](https://github.com/expressjs/express/releases)
- [Changelog](https://github.com/expressjs/express/blob/master/History.md)
- [Commits](https://github.com/expressjs/express/compare/4.18.2...4.19.2)

---
updated-dependencies:
- dependency-name: express
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
---
 website/yarn.lock | 40 ++++++++++++++++++++--------------------
 1 file changed, 20 insertions(+), 20 deletions(-)

diff --git a/website/yarn.lock b/website/yarn.lock
index 7986048..f055b6a 100644
--- a/website/yarn.lock
+++ b/website/yarn.lock
@@ -2716,13 +2716,13 @@ binary-extensions@^2.0.0:
   resolved "https://registry.yarnpkg.com/binary-extensions/-/binary-extensions-2.2.0.tgz#75f502eeaf9ffde42fc98829645be4ea76bd9e2d"
   integrity sha512-jDctJ/IVQbZoJykoeHbhXpOlNBqGNcwXJKJog42E5HDPUwQTSdjCHdihjj0DlnheQ7blbT6dHOafNAiS8ooQKA==
 
-body-parser@1.20.1:
-  version "1.20.1"
-  resolved "https://registry.yarnpkg.com/body-parser/-/body-parser-1.20.1.tgz#b1812a8912c195cd371a3ee5e66faa2338a5c668"
-  integrity sha512-jWi7abTbYwajOytWCQc37VulmWiRae5RyTpaCyDcS5/lMdtwSz5lOpDE67srw/HYe35f1z3fDQw+3txg7gNtWw==
+body-parser@1.20.2:
+  version "1.20.2"
+  resolved "https://registry.yarnpkg.com/body-parser/-/body-parser-1.20.2.tgz#6feb0e21c4724d06de7ff38da36dad4f57a747fd"
+  integrity sha512-ml9pReCu3M61kGlqoTm2umSXTlRTuGTx0bfYj+uIUKKYycG5NtSbeetV3faSU6R7ajOPw0g/J1PvK4qNy7s5bA==
   dependencies:
     bytes "3.1.2"
-    content-type "~1.0.4"
+    content-type "~1.0.5"
     debug "2.6.9"
     depd "2.0.0"
     destroy "1.2.0"
@@ -2730,7 +2730,7 @@ body-parser@1.20.1:
     iconv-lite "0.4.24"
     on-finished "2.4.1"
     qs "6.11.0"
-    raw-body "2.5.1"
+    raw-body "2.5.2"
     type-is "~1.6.18"
     unpipe "1.0.0"
 
@@ -3168,7 +3168,7 @@ content-disposition@0.5.4:
   dependencies:
     safe-buffer "5.2.1"
 
-content-type@~1.0.4:
+content-type@~1.0.4, content-type@~1.0.5:
   version "1.0.5"
   resolved "https://registry.yarnpkg.com/content-type/-/content-type-1.0.5.tgz#8b773162656d1d1086784c8f23a54ce6d73d7918"
   integrity sha512-nTjqfcBFEipKdXCv4YDQWCfmcLZKm81ldF0pAopTvyrFGVbcR6P/VAAd5G7N+0tTr8QqiU0tFadD6FK4NtJwOA==
@@ -3188,10 +3188,10 @@ cookie-signature@1.0.6:
   resolved "https://registry.yarnpkg.com/cookie-signature/-/cookie-signature-1.0.6.tgz#e303a882b342cc3ee8ca513a79999734dab3ae2c"
   integrity sha512-QADzlaHc8icV8I7vbaJXJwod9HWYp8uCqf1xa4OfNu1T7JVxQIrUgOWtHdNDtPiywmFbiS12VjotIXLrKM3orQ==
 
-cookie@0.5.0:
-  version "0.5.0"
-  resolved "https://registry.yarnpkg.com/cookie/-/cookie-0.5.0.tgz#d1f5d71adec6558c58f389987c366aa47e994f8b"
-  integrity sha512-YZ3GUyn/o8gfKJlnlX7g7xq4gyO6OSuhGPKaaGssGB2qgDUS0gPgtTvoyZLTt9Ab6dC4hfc9dV5arkvc/OCmrw==
+cookie@0.6.0:
+  version "0.6.0"
+  resolved "https://registry.yarnpkg.com/cookie/-/cookie-0.6.0.tgz#2798b04b071b0ecbff0dbb62a505a8efa4e19051"
+  integrity sha512-U71cyTamuh1CRNCfpGY6to28lxvNwPG4Guz/EVjgf3Jmzv0vlDp1atT9eS5dDjMYHucpHbWns6Lwf3BKz6svdw==
 
 copy-text-to-clipboard@^3.0.1:
   version "3.2.0"
@@ -3866,16 +3866,16 @@ execa@^5.0.0:
     strip-final-newline "^2.0.0"
 
 express@^4.17.3:
-  version "4.18.2"
-  resolved "https://registry.yarnpkg.com/express/-/express-4.18.2.tgz#3fabe08296e930c796c19e3c516979386ba9fd59"
-  integrity sha512-5/PsL6iGPdfQ/lKM1UuielYgv3BUoJfz1aUwU9vHZ+J7gyvwdQXFEBIEIaxeGf0GIcreATNyBExtalisDbuMqQ==
+  version "4.19.2"
+  resolved "https://registry.yarnpkg.com/express/-/express-4.19.2.tgz#e25437827a3aa7f2a827bc8171bbbb664a356465"
+  integrity sha512-5T6nhjsT+EOMzuck8JjBHARTHfMht0POzlA60WV2pMD3gyXw2LZnZ+ueGdNxG+0calOJcWKbpFcuzLZ91YWq9Q==
   dependencies:
     accepts "~1.3.8"
     array-flatten "1.1.1"
-    body-parser "1.20.1"
+    body-parser "1.20.2"
     content-disposition "0.5.4"
     content-type "~1.0.4"
-    cookie "0.5.0"
+    cookie "0.6.0"
     cookie-signature "1.0.6"
     debug "2.6.9"
     depd "2.0.0"
@@ -6439,10 +6439,10 @@ range-parser@^1.2.1, range-parser@~1.2.1:
   resolved "https://registry.yarnpkg.com/range-parser/-/range-parser-1.2.1.tgz#3cf37023d199e1c24d1a55b84800c2f3e6468031"
   integrity sha512-Hrgsx+orqoygnmhFbKaHE6c296J+HTAQXoxEF6gNupROmmGJRoyzfG3ccAveqCBrwr/2yxQ5BVd/GTl5agOwSg==
 
-raw-body@2.5.1:
-  version "2.5.1"
-  resolved "https://registry.yarnpkg.com/raw-body/-/raw-body-2.5.1.tgz#fe1b1628b181b700215e5fd42389f98b71392857"
-  integrity sha512-qqJBtEyVgS0ZmPGdCFPWJ3FreoqvG4MVQln/kCgF7Olq95IbOp0/BWyMwbdtn4VTvkM8Y7khCQ2Xgk/tcrCXig==
+raw-body@2.5.2:
+  version "2.5.2"
+  resolved "https://registry.yarnpkg.com/raw-body/-/raw-body-2.5.2.tgz#99febd83b90e08975087e8f1f9419a149366b68a"
+  integrity sha512-8zGqypfENjCIqGhgXToC8aB2r7YrBX+AQAfIPs/Mlk+BtPTztOvTS01NRW/3Eh60J+a48lt8qsCzirQ6loCVfA==
   dependencies:
     bytes "3.1.2"
     http-errors "2.0.0"

From e13f33a8569dd1950fbe0ed681a53306d668b5a6 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Jan=20B=C3=B6ttcher?= <jboettcher@salesforce.com>
Date: Wed, 17 Apr 2024 16:44:17 +0200
Subject: [PATCH 04/22] Add float to numeric.md

---
 website/docs/sql/datatype/numeric.md | 17 ++++++++++-------
 1 file changed, 10 insertions(+), 7 deletions(-)

diff --git a/website/docs/sql/datatype/numeric.md b/website/docs/sql/datatype/numeric.md
index 71016c8..db1a238 100644
--- a/website/docs/sql/datatype/numeric.md
+++ b/website/docs/sql/datatype/numeric.md
@@ -9,6 +9,7 @@ Name | Description
 `integer`|typical choice for integer: -2147483648 to +2147483647 (4 bytes)
 `bigint`|large-range integer: -9223372036854775808 to +9223372036854775807 (8 bytes)
 `numeric`|exact, fixed-length representation of numbers with decimal point: up to decimal 38 digits
+`real`|variable-precision, inexact: 6 decimal digits precision
 `double precision`|variable-precision, inexact: 15 decimal digits precision
 
 ## Integer Types {#int}
@@ -107,8 +108,8 @@ is not supported, yet.
 
 ## Floating-Point Type {#float}
 
-The data type `double precision` is an inexact, variable-precision
-numeric type. On all currently supported platforms, these types are
+The data type `real` and `double precision` are inexact, variable-precision
+numeric types. On all currently supported platforms, these types are
 implementations of IEEE Standard 754 for Binary Floating-Point
 Arithmetic.
 
@@ -131,7 +132,9 @@ into account when using floating-point types:
     work as expected. Using difference to a small epsilon value is
     recommended instead.
 
-On all currently supported platforms, the `double precision` type has a
+On all currently supported platforms, the `real` type has a range of around
+1E-37 and 1E+37 with a precision of at least 6 digits.
+The `double precision` type has a
 range of around 1E-307 to 1E+308 with a precision of at least 15 digits.
 Values that are too large or too small will cause an error. Rounding
 might take place if the precision of an input number is too high.
@@ -166,7 +169,7 @@ with PostgresQL and many other database systems.
 
 Hyper also supports the SQL-standard notations `float` and `float(p)`
 for specifying inexact numeric types. Here, `p` specifies the minimum
-acceptable precision in *binary* digits. However, the `p` argument is
-currently ignored and all `float(p)` types are simply mapped to
-`double precision`. `float` with no precision specified is also mapped
-to `double precision`.
+acceptable precision in *binary* digits.  Here, `p` specifies the minimum
+acceptable precision in binary digits. Hyper accepts `float(1)` to `float(24)`
+as selecting the `real` type, while `float(25)` to `float(53)` select `double precision`.
+`float` with no precision specified is also mapped to `double precision`.

From 44cb9dbfd901c956734bf5ec068563552d6b74b0 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Jan=20B=C3=B6ttcher?= <jboettcher@salesforce.com>
Date: Wed, 17 Apr 2024 17:35:17 +0200
Subject: [PATCH 05/22] Describe new file format(s)

---
 website/docs/hyper-api/hyper_process.md | 43 +++++++++++++++++++++++--
 1 file changed, 40 insertions(+), 3 deletions(-)

diff --git a/website/docs/hyper-api/hyper_process.md b/website/docs/hyper-api/hyper_process.md
index 87b9d88..04e0ab9 100644
--- a/website/docs/hyper-api/hyper_process.md
+++ b/website/docs/hyper-api/hyper_process.md
@@ -248,6 +248,45 @@ unsupported version 2 (max supported version: 1). To open this database,
 please update your product. (error code 0AS01)"
 :::
 
+##### version 3
+
+Database file format version `3` includes the improvements of file
+format version `2`. Additionally, it supports bigger numerics with a
+precision up to 38.
+Previously, Hyper only supported numerics up to 18 digits.
+The newly added bigger numerics are internally stored as 128-bit values,
+while the smaller ones still use 64-bit values.
+
+To create a new Hyper database file with this version, set
+`default_database_version=3`.
+
+
+:::note
+The database file format version `2` is supported by Tableau
+#TODO add supported Tableau versions
+:::
+
+#### version 4
+Database file format version `4` includes the improvements of file
+format version `3`. Additionally, it supports 32-bit floating points as new SQL type.
+Previously, Hyper mapped all SQL floating points to 64-bit doubles internally.
+Now, Hyper uses 32-bit floats for the SQL types `real` and `float(p)` with
+`p` lower than 25.
+The types `double precision`, `float` without a `p`, or a p `>= 25`
+still use 64-bit doubles.
+
+Old queries using the affected types might yield different results when switching
+to the new version due to the different underlying rounding behavior and arithmetics
+of 32-bit floats.
+To preserve the old behavior, the used data types must be explicitly changed
+to `double precision`.
+
+:::note
+The database file format version `4` will be supported
+in a not-yet-determined future version of Tableau.
+:::
+
+
 <!-- ### Experimental Settings {#experimentalsettings}
 
 :::warning
@@ -255,9 +294,7 @@ This section describes pre-release features that are not supported and
 should not be used in production code. Their interfaces, semantics, and
 performance characteristics are subject to change or they could be
 *removed at any time without prior notice.* There may also be bugs. If
-you encounter an issue, please [report
-it](https://github.com/tableau/hyper-db/issues).
-
+you encounter an issue, please [report it](https://github.com/tableau/hyper-db/issues).
 If you use an experimental feature in your test environment, we
 encourage you to enable telemetry in the Hyper API to help us improve
 these features. You can do so by passing the "send usage data to

From aed74b063bd370a09a41e89e642b23ee0c51faf1 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Jan=20B=C3=B6ttcher?= <jboettcher@salesforce.com>
Date: Wed, 17 Apr 2024 21:14:23 +0200
Subject: [PATCH 06/22] Add supported Tableau versions

---
 website/docs/hyper-api/hyper_process.md | 10 ++++++++--
 website/docs/releases.md                |  4 ++++
 2 files changed, 12 insertions(+), 2 deletions(-)

diff --git a/website/docs/hyper-api/hyper_process.md b/website/docs/hyper-api/hyper_process.md
index 04e0ab9..6ef78d4 100644
--- a/website/docs/hyper-api/hyper_process.md
+++ b/website/docs/hyper-api/hyper_process.md
@@ -262,8 +262,14 @@ To create a new Hyper database file with this version, set
 
 
 :::note
-The database file format version `2` is supported by Tableau
-#TODO add supported Tableau versions
+The database file format version `3` is supported by Tableau
+Desktop/Server 2022.4 and newer versions.
+Opening a database file with an unsupported
+Tableau product version will produce an error message similar to:
+
+"There was an error during loading database '[...]/file.hyper':
+unsupported version 3 (max supported version: 2). To open this database,
+please update your product. (error code 0AS01)"
 :::
 
 #### version 4
diff --git a/website/docs/releases.md b/website/docs/releases.md
index c112768..52a5c1b 100644
--- a/website/docs/releases.md
+++ b/website/docs/releases.md
@@ -28,6 +28,10 @@ In case you are wondering why all our releases start with `0.0`, read [this FAQ
 
 ### Upcoming Release
 
+* We have introduced a new 32-bit floating point data type.
+  * Persisting it is only supported in the new file format 4.
+  * A `CAST(… AS double precision)` is needed to store such columns in older file formats.
+* We announced file format 3 (bigger 128-bit numerics) and file format 4 (32-bit floating points)
 
 
 ### 0.0.18825 [March 6, 2024]

From 28b8a072c7f41c5f5d2f57a4f4fc04119e1da325 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Jan=20B=C3=B6ttcher?= <jboettcher@salesforce.com>
Date: Wed, 17 Apr 2024 21:20:32 +0200
Subject: [PATCH 07/22] Add float to datatype overview table

---
 website/docs/sql/datatype/index.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/website/docs/sql/datatype/index.md b/website/docs/sql/datatype/index.md
index f637282..9d973b4 100644
--- a/website/docs/sql/datatype/index.md
+++ b/website/docs/sql/datatype/index.md
@@ -14,6 +14,7 @@ Name|Aliases|Description
 `CHARACTER [ (n) ]`|`CHAR [ (n) ]`|fixed-length character string
 `CHARACTER VARYING (n)`|`VARCHAR (n)`|variable-length character string with limit
 `DATE`||calendar date (year, month, day)
+`REAL`|`FLOAT4`|single precision floating-point number (4 bytes)
 `DOUBLE PRECISION`|`FLOAT8`|double precision floating-point number (8 bytes)
 `INTEGER`|`INT`, `INT4`|signed four-byte integer
 `INTERVAL`||time span; not supported in Tableau

From cdb7d0ee0f3e6c68c2897ac7609c71e75cc0d4bd Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Jan=20B=C3=B6ttcher?= <jboettcher@salesforce.com>
Date: Wed, 17 Apr 2024 21:37:23 +0200
Subject: [PATCH 08/22] Add notes in numeric.md to the supported database
 versions

---
 website/docs/hyper-api/hyper_process.md | 4 ++--
 website/docs/sql/datatype/index.md      | 2 +-
 website/docs/sql/datatype/numeric.md    | 9 +++++++++
 3 files changed, 12 insertions(+), 3 deletions(-)

diff --git a/website/docs/hyper-api/hyper_process.md b/website/docs/hyper-api/hyper_process.md
index 6ef78d4..09b6fa7 100644
--- a/website/docs/hyper-api/hyper_process.md
+++ b/website/docs/hyper-api/hyper_process.md
@@ -186,7 +186,7 @@ create new database files.
 Default value: `0`
 
 Accepted values: `0`, `1` (writing this version is deprecated in favor
-of version 2 and will be removed in a future Hyper API release), `2`
+of version 2 and will be removed in a future Hyper API release), `2`, `3`, and `4`.
 
 ##### version 0
 
@@ -278,7 +278,7 @@ format version `3`. Additionally, it supports 32-bit floating points as new SQL
 Previously, Hyper mapped all SQL floating points to 64-bit doubles internally.
 Now, Hyper uses 32-bit floats for the SQL types `real` and `float(p)` with
 `p` lower than 25.
-The types `double precision`, `float` without a `p`, or a p `>= 25`
+The types `double precision`, `float`, or `float(p)` with p `>= 25`
 still use 64-bit doubles.
 
 Old queries using the affected types might yield different results when switching
diff --git a/website/docs/sql/datatype/index.md b/website/docs/sql/datatype/index.md
index 9d973b4..8ab892a 100644
--- a/website/docs/sql/datatype/index.md
+++ b/website/docs/sql/datatype/index.md
@@ -32,4 +32,4 @@ Links to detailed documentation:
 import DocCardList from '@theme/DocCardList';
 
 <DocCardList />
-```
\ No newline at end of file
+```
diff --git a/website/docs/sql/datatype/numeric.md b/website/docs/sql/datatype/numeric.md
index db1a238..7159925 100644
--- a/website/docs/sql/datatype/numeric.md
+++ b/website/docs/sql/datatype/numeric.md
@@ -40,6 +40,10 @@ Precisions over 18 require 128-bit for internal storage. Processing
 so it is advisable to use a sensible precision for the use case at hand
 instead of always using the maximum precision by default.
 
+:::note
+128-bit numerics can only be stored using [database version 3](../../hyper-api/hyper_process#version 3) or newer.
+:::
+
 Both the maximum precision and the maximum scale of a `numeric` column
 can be configured. To declare a column of type `numeric` use the syntax
 `NUMERIC(precision, scale)`. The precision must be positive, the scale zero or positive.
@@ -141,6 +145,11 @@ might take place if the precision of an input number is too high.
 Numbers too close to zero that are not representable as distinct from
 zero will cause an underflow error.
 
+:::note
+32-bit floating points are only used with [database version 4](../../hyper-api/hyper_process#version 4)
+or newer.
+:::
+
 By default, floating point values are output in text form in their
 shortest precise decimal representation; the decimal value produced is
 closer to the true stored binary value than to any other value

From 7aaff35a632db843affe8e4aa40e67faa954e2ba Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Jan=20B=C3=B6ttcher?= <jboettcher@salesforce.com>
Date: Wed, 17 Apr 2024 22:07:33 +0200
Subject: [PATCH 09/22] Cleanup/Fix links

---
 website/docs/hyper-api/hyper_process.md | 7 +++++--
 website/docs/sql/datatype/index.md      | 9 +++++++++
 website/docs/sql/datatype/numeric.md    | 6 +++---
 3 files changed, 17 insertions(+), 5 deletions(-)

diff --git a/website/docs/hyper-api/hyper_process.md b/website/docs/hyper-api/hyper_process.md
index 09b6fa7..52d7cb6 100644
--- a/website/docs/hyper-api/hyper_process.md
+++ b/website/docs/hyper-api/hyper_process.md
@@ -277,8 +277,8 @@ Database file format version `4` includes the improvements of file
 format version `3`. Additionally, it supports 32-bit floating points as new SQL type.
 Previously, Hyper mapped all SQL floating points to 64-bit doubles internally.
 Now, Hyper uses 32-bit floats for the SQL types `real` and `float(p)` with
-`p` lower than 25.
-The types `double precision`, `float`, or `float(p)` with p `>= 25`
+`p <= 24`.
+The types `double precision`, `float`, or `float(p)` with `p >= 25`
 still use 64-bit doubles.
 
 Old queries using the affected types might yield different results when switching
@@ -287,6 +287,9 @@ of 32-bit floats.
 To preserve the old behavior, the used data types must be explicitly changed
 to `double precision`.
 
+To create a new Hyper database file with this version, set
+`default_database_version=4`.
+
 :::note
 The database file format version `4` will be supported
 in a not-yet-determined future version of Tableau.
diff --git a/website/docs/sql/datatype/index.md b/website/docs/sql/datatype/index.md
index 8ab892a..7ba655d 100644
--- a/website/docs/sql/datatype/index.md
+++ b/website/docs/sql/datatype/index.md
@@ -26,6 +26,15 @@ Name|Aliases|Description
 `TIMESTAMP WITH TIME ZONE`|`TIMESTAMPTZ`|date and time, including time zone
 `GEOGRAPHY`||a geography object
 
+:::note
+`Numerics` with a precision greater than 18 are only supported with a [database version 3](../../hyper-api/hyper_process#version-3) or newer.
+:::
+:::note
+The 32-bit floating point type `real` was introduced with [database version 4](../../hyper-api/hyper_process#version-4).
+Previously, all floating points were mapped to 64-bit `double precision`.
+:::
+
+
 Links to detailed documentation:
 
 ```mdx-code-block
diff --git a/website/docs/sql/datatype/numeric.md b/website/docs/sql/datatype/numeric.md
index 7159925..ef15e3f 100644
--- a/website/docs/sql/datatype/numeric.md
+++ b/website/docs/sql/datatype/numeric.md
@@ -41,7 +41,7 @@ so it is advisable to use a sensible precision for the use case at hand
 instead of always using the maximum precision by default.
 
 :::note
-128-bit numerics can only be stored using [database version 3](../../hyper-api/hyper_process#version 3) or newer.
+128-bit numerics can only be stored using [database version 3](../../hyper-api/hyper_process#version-3) or newer.
 :::
 
 Both the maximum precision and the maximum scale of a `numeric` column
@@ -146,8 +146,8 @@ Numbers too close to zero that are not representable as distinct from
 zero will cause an underflow error.
 
 :::note
-32-bit floating points are only used with [database version 4](../../hyper-api/hyper_process#version 4)
-or newer.
+32-bit floating points were only introduced with [database version 4](../../hyper-api/hyper_process#version-4).
+Previously, all floating points used the 64-bit `double precision`.
 :::
 
 By default, floating point values are output in text form in their

From 059db2c76a2fa91b38b61f92b7c1e9900749b304 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Jan=20B=C3=B6ttcher?= <jboettcher@salesforce.com>
Date: Thu, 18 Apr 2024 09:51:40 +0200
Subject: [PATCH 10/22] Deduplicate every version includes improvements...

---
 website/docs/hyper-api/hyper_process.md | 19 +++++++++++--------
 1 file changed, 11 insertions(+), 8 deletions(-)

diff --git a/website/docs/hyper-api/hyper_process.md b/website/docs/hyper-api/hyper_process.md
index 52d7cb6..baaec82 100644
--- a/website/docs/hyper-api/hyper_process.md
+++ b/website/docs/hyper-api/hyper_process.md
@@ -173,7 +173,7 @@ These settings control Hyper's database files.
 Newer database file format versions than the initial version `0` are
 unsupported in older product versions. This means that you can use newer
 database versions with the latest Hyper API and newer product versions
-but you cannot open them in older product versions. For example, the new
+but you cannot open them in older product versions. For example, the
 database file format version `2` can be opened in Tableau Desktop
 2020.4.15 but it cannot be opened in Tableau Desktop 2020.3. The
 complete compatibility matrix is documented in the version sections
@@ -188,6 +188,12 @@ Default value: `0`
 Accepted values: `0`, `1` (writing this version is deprecated in favor
 of version 2 and will be removed in a future Hyper API release), `2`, `3`, and `4`.
 
+:::note
+Every version builds on the improvements of the previous version(s) and
+adds some new functionality, like new data types.
+:::
+
+
 ##### version 0
 
 The default and initial database file format version is version `0`. It
@@ -229,8 +235,7 @@ please update your product. (error code 0AS01)"
 
 ##### version 2
 
-Database file format version `2` includes the improvements of file
-format version `1`. Additionally, it supports storing and querying
+Database file format version `2` adds support for storing and querying
 textual data with arbitrary versions of the Unicode collation tables.
 
 To create a new Hyper database file with this version, set
@@ -250,8 +255,7 @@ please update your product. (error code 0AS01)"
 
 ##### version 3
 
-Database file format version `3` includes the improvements of file
-format version `2`. Additionally, it supports bigger numerics with a
+Database file format version `3` adds support for bigger numerics with a
 precision up to 38.
 Previously, Hyper only supported numerics up to 18 digits.
 The newly added bigger numerics are internally stored as 128-bit values,
@@ -273,9 +277,8 @@ please update your product. (error code 0AS01)"
 :::
 
 #### version 4
-Database file format version `4` includes the improvements of file
-format version `3`. Additionally, it supports 32-bit floating points as new SQL type.
-Previously, Hyper mapped all SQL floating points to 64-bit doubles internally.
+Database file format version `4` adds support for a new 32-bit floating point type.
+Previously, Hyper internally mapped all SQL floating points to 64-bit doubles.
 Now, Hyper uses 32-bit floats for the SQL types `real` and `float(p)` with
 `p <= 24`.
 The types `double precision`, `float`, or `float(p)` with `p >= 25`

From 1fc8dff7de8e6aa2bf8ba2969c1beaa55b9b60be Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Jan=20B=C3=B6ttcher?= <jboettcher@salesforce.com>
Date: Thu, 18 Apr 2024 10:03:09 +0200
Subject: [PATCH 11/22] Deduplicate error message for wrong database version
 and restructure slightly

---
 website/docs/hyper-api/hyper_process.md | 53 ++++++++-----------------
 1 file changed, 17 insertions(+), 36 deletions(-)

diff --git a/website/docs/hyper-api/hyper_process.md b/website/docs/hyper-api/hyper_process.md
index baaec82..63e7d3d 100644
--- a/website/docs/hyper-api/hyper_process.md
+++ b/website/docs/hyper-api/hyper_process.md
@@ -169,6 +169,16 @@ These settings control Hyper's database files.
 
 #### default_database_version
 
+Specifies the default database file format version that will be used to
+create new database files.
+Every version builds on the improvements of the previous version(s) and
+adds some new functionality, like new data types.
+
+Default value: `0`
+
+Accepted values: `0`, `1` (writing this version is deprecated in favor
+of version 2 and will be removed in a future Hyper API release), `2`, `3`, and `4`.
+
 :::note
 Newer database file format versions than the initial version `0` are
 unsupported in older product versions. This means that you can use newer
@@ -178,19 +188,13 @@ database file format version `2` can be opened in Tableau Desktop
 2020.4.15 but it cannot be opened in Tableau Desktop 2020.3. The
 complete compatibility matrix is documented in the version sections
 below.
-:::
 
-Specifies the default database file format version that will be used to
-create new database files.
-
-Default value: `0`
-
-Accepted values: `0`, `1` (writing this version is deprecated in favor
-of version 2 and will be removed in a future Hyper API release), `2`, `3`, and `4`.
+Opening a database file with an unsupported
+Tableau product version will produce an error message similar to:
 
-:::note
-Every version builds on the improvements of the previous version(s) and
-adds some new functionality, like new data types.
+"There was an error during loading database '[...]/file.hyper':
+unsupported version 3 (max supported version: 2). To open this database,
+please update your product. (error code 0AS01)"
 :::
 
 
@@ -225,12 +229,6 @@ and will be removed in a future Hyper API release.
 The database file format version `1` is supported by Tableau
 Desktop/Server 2019.2.10, 2019.3.6, 2019.4.5, 2020.1.1 and newer product
 versions. It is supported by Tableau Prep 2020.2 and newer versions.
-Opening a database file with an unsupported Tableau product version will
-produce an error message similar to:
-
-"There was an error during loading database '[...]/file.hyper':
-unsupported version 1 (max supported version: 0). To open this database,
-please update your product. (error code 0AS01)"
 :::
 
 ##### version 2
@@ -245,12 +243,7 @@ To create a new Hyper database file with this version, set
 The database file format version `2` is supported by Tableau
 Desktop/Server 2020.4.15, 2021.1.12, 2021.2.9, 2021.3.8, 2021.4.4,
 2022.1.2 and newer product versions. It is supported by Tableau Prep
-2022.3 and newer versions. Opening a database file with an unsupported
-Tableau product version will produce an error message similar to:
-
-"There was an error during loading database '[...]/file.hyper':
-unsupported version 2 (max supported version: 1). To open this database,
-please update your product. (error code 0AS01)"
+2022.3 and newer versions.
 :::
 
 ##### version 3
@@ -259,23 +252,11 @@ Database file format version `3` adds support for bigger numerics with a
 precision up to 38.
 Previously, Hyper only supported numerics up to 18 digits.
 The newly added bigger numerics are internally stored as 128-bit values,
-while the smaller ones still use 64-bit values.
+while smaller ones still use 64-bit values.
 
 To create a new Hyper database file with this version, set
 `default_database_version=3`.
 
-
-:::note
-The database file format version `3` is supported by Tableau
-Desktop/Server 2022.4 and newer versions.
-Opening a database file with an unsupported
-Tableau product version will produce an error message similar to:
-
-"There was an error during loading database '[...]/file.hyper':
-unsupported version 3 (max supported version: 2). To open this database,
-please update your product. (error code 0AS01)"
-:::
-
 #### version 4
 Database file format version `4` adds support for a new 32-bit floating point type.
 Previously, Hyper internally mapped all SQL floating points to 64-bit doubles.

From 0ff798c4877d54afde264ea438cc3885b320eb87 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Jan=20B=C3=B6ttcher?= <jboettcher@salesforce.com>
Date: Thu, 18 Apr 2024 12:41:59 +0200
Subject: [PATCH 12/22] Overhauled release and database version 4 section

---
 website/docs/hyper-api/hyper_process.md | 17 ++++++-----------
 website/docs/releases.md                | 18 +++++++++++++++---
 2 files changed, 21 insertions(+), 14 deletions(-)

diff --git a/website/docs/hyper-api/hyper_process.md b/website/docs/hyper-api/hyper_process.md
index 63e7d3d..3c274ef 100644
--- a/website/docs/hyper-api/hyper_process.md
+++ b/website/docs/hyper-api/hyper_process.md
@@ -258,18 +258,13 @@ To create a new Hyper database file with this version, set
 `default_database_version=3`.
 
 #### version 4
-Database file format version `4` adds support for a new 32-bit floating point type.
-Previously, Hyper internally mapped all SQL floating points to 64-bit doubles.
-Now, Hyper uses 32-bit floats for the SQL types `real` and `float(p)` with
-`p <= 24`.
-The types `double precision`, `float`, or `float(p)` with `p >= 25`
-still use 64-bit doubles.
+Database file format version `4` was introduced to support
+persisting and reading the new 32-bit floating point type.
 
-Old queries using the affected types might yield different results when switching
-to the new version due to the different underlying rounding behavior and arithmetics
-of 32-bit floats.
-To preserve the old behavior, the used data types must be explicitly changed
-to `double precision`.
+Starting with release (#TODO), Hyper uses 32-bit floats for
+the SQL types `real` and `float(p)` with `p <= 24`.
+The types `double precision`, `float`, and `float(p)` with `p >= 25`
+still use 64-bit doubles.
 
 To create a new Hyper database file with this version, set
 `default_database_version=4`.
diff --git a/website/docs/releases.md b/website/docs/releases.md
index 52a5c1b..c98a23b 100644
--- a/website/docs/releases.md
+++ b/website/docs/releases.md
@@ -28,11 +28,23 @@ In case you are wondering why all our releases start with `0.0`, read [this FAQ
 
 ### Upcoming Release
 
-* We have introduced a new 32-bit floating point data type.
-  * Persisting it is only supported in the new file format 4.
+!!!
+
+TODO: Update release number (#TODO) in database version [database version 4](hyper-api/hyper_process#version-4) when doing this release!!!
+
+!!!
+
+* Announced [database version 3](hyper-api/hyper_process#version-3) that is able to store [`128-bit NUMERICS`](/docs/sql/datatype/numeric#numeric-decimal).
+* Introduced a new 32-bit floating point data type for `REAL`.
+  * Previously, `REAL` was internally mapped to 64-bit `DOUBLE PRECISION`.
+  * Introduced new [database version 4](hyper-api/hyper_process#version-4) to support reading and persisting the new 32-bit floats.
   * A `CAST(… AS double precision)` is needed to store such columns in older file formats.
-* We announced file format 3 (bigger 128-bit numerics) and file format 4 (32-bit floating points)
 
+:::warning
+Queries using `REAL`, `FLOAT4`, or `FLOAT(p)` with `p <= 24` are now treated as `32 bit` floating points.
+This can lead to different results due to the different underlying rounding behavior and arithmetics of 32-bit floats.
+To preserve the old behavior, the used data types must be explicitly changed or cast to `DOUBLE PRECISION`.
+:::
 
 ### 0.0.18825 [March 6, 2024]
 

From 333425e55a5072237a9ecfb062396e3b494702f8 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Jan=20B=C3=B6ttcher?= <jboettcher@salesforce.com>
Date: Thu, 18 Apr 2024 12:56:22 +0200
Subject: [PATCH 13/22] Refined data types page

---
 website/docs/sql/datatype/index.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/website/docs/sql/datatype/index.md b/website/docs/sql/datatype/index.md
index 7ba655d..055c646 100644
--- a/website/docs/sql/datatype/index.md
+++ b/website/docs/sql/datatype/index.md
@@ -27,11 +27,11 @@ Name|Aliases|Description
 `GEOGRAPHY`||a geography object
 
 :::note
-`Numerics` with a precision greater than 18 are only supported with a [database version 3](../../hyper-api/hyper_process#version-3) or newer.
+Persisting `NUMERICs` with a precision greater than 18 requires at least [database version 3](/docs/hyper-api/hyper_process#version-3).
 :::
 :::note
-The 32-bit floating point type `real` was introduced with [database version 4](../../hyper-api/hyper_process#version-4).
-Previously, all floating points were mapped to 64-bit `double precision`.
+Persisting 32-bit `REALs` requires at least [database version 4](/docs/hyper-api/hyper_process#version-4).
+Up until Hyper API release [0.0.18825](/docs/releases#0.0.18825) Hyper mapped all floating points internally to 64-bit `DOUBLE PRECISIONs`.
 :::
 
 

From 7dae7c9db3ec1be87b938bea2a8b7210ac011789 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Jan=20B=C3=B6ttcher?= <jboettcher@salesforce.com>
Date: Thu, 18 Apr 2024 13:01:15 +0200
Subject: [PATCH 14/22] Typos

---
 website/docs/sql/datatype/numeric.md | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/website/docs/sql/datatype/numeric.md b/website/docs/sql/datatype/numeric.md
index ef15e3f..3bc30f9 100644
--- a/website/docs/sql/datatype/numeric.md
+++ b/website/docs/sql/datatype/numeric.md
@@ -41,7 +41,7 @@ so it is advisable to use a sensible precision for the use case at hand
 instead of always using the maximum precision by default.
 
 :::note
-128-bit numerics can only be stored using [database version 3](../../hyper-api/hyper_process#version-3) or newer.
+128-bit numerics can only be stored using [database version 3](/docs/hyper-api/hyper_process#version-3) or newer.
 :::
 
 Both the maximum precision and the maximum scale of a `numeric` column
@@ -112,9 +112,9 @@ is not supported, yet.
 
 ## Floating-Point Type {#float}
 
-The data type `real` and `double precision` are inexact, variable-precision
+The data types `real` and `double precision` are inexact, variable-precision
 numeric types. On all currently supported platforms, these types are
-implementations of IEEE Standard 754 for Binary Floating-Point
+implementations of the IEEE Standard 754 for Binary Floating-Point
 Arithmetic.
 
 Inexact means that some values cannot be converted exactly to the
@@ -146,8 +146,8 @@ Numbers too close to zero that are not representable as distinct from
 zero will cause an underflow error.
 
 :::note
-32-bit floating points were only introduced with [database version 4](../../hyper-api/hyper_process#version-4).
-Previously, all floating points used the 64-bit `double precision`.
+32-bit floating points can only be stored with
+[database version 4](/docs/hyper-api/hyper_process#version-4) or newer.
 :::
 
 By default, floating point values are output in text form in their

From 42d8dc9464773326076a8165f9e78dbb630c40a0 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Jan=20B=C3=B6ttcher?=
 <6001032+jboettcher@users.noreply.github.com>
Date: Thu, 18 Apr 2024 13:02:01 +0200
Subject: [PATCH 15/22] Update website/docs/sql/datatype/numeric.md

Co-authored-by: Adrian Vogelsgesang <adrian.vogelsgesang@tum.de>
---
 website/docs/sql/datatype/numeric.md | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/website/docs/sql/datatype/numeric.md b/website/docs/sql/datatype/numeric.md
index 3bc30f9..a0118ae 100644
--- a/website/docs/sql/datatype/numeric.md
+++ b/website/docs/sql/datatype/numeric.md
@@ -179,6 +179,7 @@ with PostgresQL and many other database systems.
 Hyper also supports the SQL-standard notations `float` and `float(p)`
 for specifying inexact numeric types. Here, `p` specifies the minimum
 acceptable precision in *binary* digits.  Here, `p` specifies the minimum
-acceptable precision in binary digits. Hyper accepts `float(1)` to `float(24)`
-as selecting the `real` type, while `float(25)` to `float(53)` select `double precision`.
-`float` with no precision specified is also mapped to `double precision`.
+acceptable precision in binary digits. The types `float(1)` to `float(24)`
+are mapped to the `real` type. The types `float(25)` to `float(53)` map
+to `double precision`. `float` with no precision specified also maps
+to `double precision`.

From 4eea5e24ac1a2e03516aa2d8c92192e821ae96f7 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Jan=20B=C3=B6ttcher?= <jboettcher@salesforce.com>
Date: Thu, 18 Apr 2024 14:03:09 +0200
Subject: [PATCH 16/22] Remove new lines

---
 website/docs/hyper-api/hyper_process.md | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/website/docs/hyper-api/hyper_process.md b/website/docs/hyper-api/hyper_process.md
index 163c705..2aa3a63 100644
--- a/website/docs/hyper-api/hyper_process.md
+++ b/website/docs/hyper-api/hyper_process.md
@@ -246,9 +246,6 @@ Desktop/Server 2020.4.15, 2021.1.12, 2021.2.9, 2021.3.8, 2021.4.4,
 2022.3 and newer versions.
 :::
 
-
-
-
 ##### version 3
 
 Database file format version `3` supports storing and querying 128-bit

From 5424d4fcd151e8b852239788530dac78684ea3fa Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Jan=20B=C3=B6ttcher?=
 <6001032+jboettcher@users.noreply.github.com>
Date: Thu, 18 Apr 2024 16:47:43 +0200
Subject: [PATCH 17/22] Update website/docs/releases.md

Co-authored-by: wolfroediger <109283644+wolfroediger@users.noreply.github.com>
---
 website/docs/releases.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/docs/releases.md b/website/docs/releases.md
index d239ea8..205e140 100644
--- a/website/docs/releases.md
+++ b/website/docs/releases.md
@@ -34,11 +34,11 @@ TODO: Update release number (#TODO) in database version [database version 4](hyp
 
 !!!
 
-* Documented the new and improved [database file format version 3](hyper-api/hyper_process#version-3) that was introduced in version 0.0.16123. The new format supports 128-bit numerics. Refer to [Hyper Database Settings](/docs/hyper-api/hyper_process#default_database_version) for more information.
 * Introduced a new 32-bit floating point data type for `REAL`.
   * Previously, `REAL` was internally mapped to 64-bit `DOUBLE PRECISION`.
   * Introduced new [database file format version 4](hyper-api/hyper_process#version-4) to support reading and persisting the new 32-bit floats.
   * A `CAST(… AS double precision)` is needed to store such columns in older file formats.
+* Documented the new and improved [database file format version 3](hyper-api/hyper_process#version-3) that was introduced in version 0.0.16123. The new format supports 128-bit numerics. Refer to [Hyper Database Settings](/docs/hyper-api/hyper_process#default_database_version) for more information.
 
 :::warning
 Queries using `REAL`, `FLOAT4`, or `FLOAT(p)` with `p <= 24` are now treated as `32 bit` floating points.

From bd038217fd189be481e2e21fd8fef7dd7d177fbd Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Jan=20B=C3=B6ttcher?=
 <6001032+jboettcher@users.noreply.github.com>
Date: Thu, 18 Apr 2024 16:48:06 +0200
Subject: [PATCH 18/22] Update website/docs/releases.md

Co-authored-by: wolfroediger <109283644+wolfroediger@users.noreply.github.com>
---
 website/docs/releases.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/docs/releases.md b/website/docs/releases.md
index 205e140..af6b214 100644
--- a/website/docs/releases.md
+++ b/website/docs/releases.md
@@ -43,7 +43,7 @@ TODO: Update release number (#TODO) in database version [database version 4](hyp
 :::warning
 Queries using `REAL`, `FLOAT4`, or `FLOAT(p)` with `p <= 24` are now treated as `32 bit` floating points.
 This can lead to different results due to the different underlying rounding behavior and arithmetics of 32-bit floats.
-To preserve the old behavior, the used data types must be explicitly changed or cast to `DOUBLE PRECISION`.
+To preserve the old behavior, you need to use the types `DOUBLE PRECISION`, `FLOAT8`, or `FLOAT(p)` with `p >= 25`. These continue to be treated as 64-bit floating points.
 :::
 
 ### 0.0.18825 [March 6, 2024]

From 86d12d7ad9f81cd1d90835797b9a8a79fd93f48d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Jan=20B=C3=B6ttcher?= <jboettcher@salesforce.com>
Date: Thu, 18 Apr 2024 16:57:10 +0200
Subject: [PATCH 19/22] Wolf's feedback on datatypes/index.md

---
 website/docs/sql/datatype/index.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/website/docs/sql/datatype/index.md b/website/docs/sql/datatype/index.md
index 055c646..c6bd9f0 100644
--- a/website/docs/sql/datatype/index.md
+++ b/website/docs/sql/datatype/index.md
@@ -15,7 +15,7 @@ Name|Aliases|Description
 `CHARACTER VARYING (n)`|`VARCHAR (n)`|variable-length character string with limit
 `DATE`||calendar date (year, month, day)
 `REAL`|`FLOAT4`|single precision floating-point number (4 bytes)
-`DOUBLE PRECISION`|`FLOAT8`|double precision floating-point number (8 bytes)
+`DOUBLE PRECISION`|`FLOAT`, `FLOAT8`|double precision floating-point number (8 bytes)
 `INTEGER`|`INT`, `INT4`|signed four-byte integer
 `INTERVAL`||time span; not supported in Tableau
 `NUMERIC [ (p, s) ]`|`DECIMAL [ (p, s) ]`|exact numeric of selectable precision
@@ -27,11 +27,11 @@ Name|Aliases|Description
 `GEOGRAPHY`||a geography object
 
 :::note
-Persisting `NUMERICs` with a precision greater than 18 requires at least [database version 3](/docs/hyper-api/hyper_process#version-3).
+Persisting `NUMERIC`s with a precision greater than 18 requires at least [database version 3](/docs/hyper-api/hyper_process#version-3).
 :::
 :::note
-Persisting 32-bit `REALs` requires at least [database version 4](/docs/hyper-api/hyper_process#version-4).
-Up until Hyper API release [0.0.18825](/docs/releases#0.0.18825) Hyper mapped all floating points internally to 64-bit `DOUBLE PRECISIONs`.
+Persisting 32-bit floating point values (e.g., type `REAL`) requires at least [database version 4](/docs/hyper-api/hyper_process#version-4).
+Up until Hyper API release [0.0.18825](/docs/releases#0.0.18825) Hyper used 64-bit floating points for all float types (i.e., also for `REAL`).
 :::
 
 

From 6f626462f0db4377e99e2127b6da933c1d31464d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Jan=20B=C3=B6ttcher?=
 <6001032+jboettcher@users.noreply.github.com>
Date: Thu, 18 Apr 2024 16:59:07 +0200
Subject: [PATCH 20/22] Update website/docs/releases.md

Co-authored-by: wolfroediger <109283644+wolfroediger@users.noreply.github.com>
---
 website/docs/releases.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/docs/releases.md b/website/docs/releases.md
index af6b214..b271b69 100644
--- a/website/docs/releases.md
+++ b/website/docs/releases.md
@@ -42,7 +42,7 @@ TODO: Update release number (#TODO) in database version [database version 4](hyp
 
 :::warning
 Queries using `REAL`, `FLOAT4`, or `FLOAT(p)` with `p <= 24` are now treated as `32 bit` floating points.
-This can lead to different results due to the different underlying rounding behavior and arithmetics of 32-bit floats.
+This can lead to different results due to the reduced precision of 32-bit floating points.
 To preserve the old behavior, you need to use the types `DOUBLE PRECISION`, `FLOAT8`, or `FLOAT(p)` with `p >= 25`. These continue to be treated as 64-bit floating points.
 :::
 

From 4c81d7d034b761690d984ecbd22c37e70f8ee24c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Jan=20B=C3=B6ttcher?=
 <6001032+jboettcher@users.noreply.github.com>
Date: Thu, 18 Apr 2024 16:59:17 +0200
Subject: [PATCH 21/22] Update website/docs/releases.md

Co-authored-by: wolfroediger <109283644+wolfroediger@users.noreply.github.com>
---
 website/docs/releases.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/docs/releases.md b/website/docs/releases.md
index b271b69..5c9fc20 100644
--- a/website/docs/releases.md
+++ b/website/docs/releases.md
@@ -41,7 +41,7 @@ TODO: Update release number (#TODO) in database version [database version 4](hyp
 * Documented the new and improved [database file format version 3](hyper-api/hyper_process#version-3) that was introduced in version 0.0.16123. The new format supports 128-bit numerics. Refer to [Hyper Database Settings](/docs/hyper-api/hyper_process#default_database_version) for more information.
 
 :::warning
-Queries using `REAL`, `FLOAT4`, or `FLOAT(p)` with `p <= 24` are now treated as `32 bit` floating points.
+Queries using `REAL`, `FLOAT4`, or `FLOAT(p)` with `p <= 24` are now treated as 32-bit floating points.
 This can lead to different results due to the reduced precision of 32-bit floating points.
 To preserve the old behavior, you need to use the types `DOUBLE PRECISION`, `FLOAT8`, or `FLOAT(p)` with `p >= 25`. These continue to be treated as 64-bit floating points.
 :::

From c150724ae4adfce1b6eaee1d2c8c22ae568ad06a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Jan=20B=C3=B6ttcher?= <jboettcher@salesforce.com>
Date: Thu, 18 Apr 2024 17:01:24 +0200
Subject: [PATCH 22/22] Mention float4 and float8

---
 website/docs/hyper-api/hyper_process.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/website/docs/hyper-api/hyper_process.md b/website/docs/hyper-api/hyper_process.md
index 2aa3a63..3c71d82 100644
--- a/website/docs/hyper-api/hyper_process.md
+++ b/website/docs/hyper-api/hyper_process.md
@@ -266,8 +266,8 @@ Database file format version `4` was introduced to support
 persisting and reading the new 32-bit floating point type.
 
 Starting with release (#TODO), Hyper uses 32-bit floats for
-the SQL types `real` and `float(p)` with `p <= 24`.
-The types `double precision`, `float`, and `float(p)` with `p >= 25`
+the SQL types `real`, `float4`, and `float(p)` with `p <= 24`.
+The types `double precision`, `float`, `float8`, and `float(p)` with `p >= 25`
 still use 64-bit doubles.
 
 To create a new Hyper database file with this version, set