Merge branch 'release_4.3' into release_4.4

kriszyp · kriszyp · commit 348426bbdd38 · 2024-11-19T09:06:21.000-07:00
diff --git a/docs/SUMMARY.md b/docs/SUMMARY.md
@@ -128,6 +128,7 @@
     * [4.4.2](technical-details/release-notes/4.tucker/4.4.2.md)
     * [4.4.1](technical-details/release-notes/4.tucker/4.4.1.md)
     * [4.4.0](technical-details/release-notes/4.tucker/4.4.0.md)
+    * [4.3.36](technical-details/release-notes/4.tucker/4.3.36.md)
     * [4.3.35](technical-details/release-notes/4.tucker/4.3.35.md)
     * [4.3.34](technical-details/release-notes/4.tucker/4.3.34.md)
     * [4.3.33](technical-details/release-notes/4.tucker/4.3.33.md)
diff --git a/docs/developers/operations-api/sql-operations.md b/docs/developers/operations-api/sql-operations.md
@@ -1,3 +1,7 @@
+{% hint style="warning" %}
+HarperDB encourages developers to utilize other querying tools over SQL for performance purposes. HarperDB SQL is intended for data investigation purposes and uses cases where performance is not a priority. SQL optimizations are on our roadmap for the future.
+{% endhint %}
+
 # SQL Operations 
 
 ## Select
diff --git a/docs/developers/sql-guide/date-functions.md b/docs/developers/sql-guide/date-functions.md
@@ -1,3 +1,7 @@
+{% hint style="warning" %}
+HarperDB encourages developers to utilize other querying tools over SQL for performance purposes. HarperDB SQL is intended for data investigation purposes and uses cases where performance is not a priority. SQL optimizations are on our roadmap for the future.
+{% endhint %}
+
 # SQL Date Functions
 
 HarperDB utilizes [Coordinated Universal Time (UTC)](https://en.wikipedia.org/wiki/Coordinated_Universal_Time) in all internal SQL operations. This means that date values passed into any of the functions below will be assumed to be in UTC or in a format that can be translated to UTC.
diff --git a/docs/developers/sql-guide/features-matrix.md b/docs/developers/sql-guide/features-matrix.md
@@ -1,3 +1,7 @@
+{% hint style="warning" %}
+HarperDB encourages developers to utilize other querying tools over SQL for performance purposes. HarperDB SQL is intended for data investigation purposes and uses cases where performance is not a priority. SQL optimizations are on our roadmap for the future.
+{% endhint %}
+
 # SQL Features Matrix
 
 HarperDB provides access to most SQL functions, and we’re always expanding that list. Check below to see if we cover what you need. If not, feel free to [add a Feature Request](https://feedback.harperdb.io/).
diff --git a/docs/developers/sql-guide/functions.md b/docs/developers/sql-guide/functions.md
@@ -1,3 +1,7 @@
+{% hint style="warning" %}
+HarperDB encourages developers to utilize other querying tools over SQL for performance purposes. HarperDB SQL is intended for data investigation purposes and uses cases where performance is not a priority. SQL optimizations are on our roadmap for the future.
+{% endhint %}
+
 # HarperDB SQL Functions
 
 This SQL keywords reference contains the SQL functions available in HarperDB.
diff --git a/docs/developers/sql-guide/json-search.md b/docs/developers/sql-guide/json-search.md
@@ -1,3 +1,7 @@
+{% hint style="warning" %}
+HarperDB encourages developers to utilize other querying tools over SQL for performance purposes. HarperDB SQL is intended for data investigation purposes and uses cases where performance is not a priority. SQL optimizations are on our roadmap for the future.
+{% endhint %}
+
 # SQL JSON Search
 
 HarperDB automatically indexes all top level attributes in a row / object written to a table. However, any attributes which hold JSON data do not have their nested attributes indexed. In order to make searching and/or transforming these JSON documents easy, HarperDB offers a special SQL function called SEARCH\_JSON. The SEARCH\_JSON function works in SELECT & WHERE clauses allowing queries to perform powerful filtering on any element of your JSON by implementing the [JSONata library](http://docs.jsonata.org/overview.html) into our SQL engine.
diff --git a/docs/developers/sql-guide/reserved-word.md b/docs/developers/sql-guide/reserved-word.md
@@ -1,3 +1,7 @@
+{% hint style="warning" %}
+HarperDB encourages developers to utilize other querying tools over SQL for performance purposes. HarperDB SQL is intended for data investigation purposes and uses cases where performance is not a priority. SQL optimizations are on our roadmap for the future.
+{% endhint %}
+
 # HarperDB SQL Reserved Words
 
 This is a list of reserved words in the SQL Parser.  Use of these words or symbols may result in unexpected behavior or inaccessible tables/attributes.  If any of these words must be used, any SQL call referencing a database, table, or attribute must have backticks (`…`) or brackets ([…]) around the variable.
diff --git a/docs/developers/sql-guide/sql-geospatial-functions.md b/docs/developers/sql-guide/sql-geospatial-functions.md
@@ -1,3 +1,7 @@
+{% hint style="warning" %}
+HarperDB encourages developers to utilize other querying tools over SQL for performance purposes. HarperDB SQL is intended for data investigation purposes and uses cases where performance is not a priority. SQL optimizations are on our roadmap for the future.
+{% endhint %}
+
 # SQL Geospatial Functions
 
 HarperDB geospatial features require data to be stored in a single column using the [GeoJSON standard](http://geojson.org/), a standard commonly used in geospatial technologies. Geospatial functions are available to be used in SQL statements.
diff --git a/docs/technical-details/release-notes/4.tucker/4.3.36.md b/docs/technical-details/release-notes/4.tucker/4.3.36.md
@@ -0,0 +1,4 @@
+### HarperDB 4.3.35
+11/14/2024
+
+* lmdb-js upgrade for better free-space management
diff --git a/docs/technical-details/release-notes/README.md b/docs/technical-details/release-notes/README.md
@@ -16,6 +16,8 @@
 
 [4.4.0 Tucker](4.tucker/4.4.0.md)
 
+[4.3.36 Tucker](4.tucker/4.3.36.md)
+
 [4.3.35 Tucker](4.tucker/4.3.35.md)
 
 [4.3.34 Tucker](4.tucker/4.3.34.md)
