3.31 release notes 2.0

docs/Reference/release-notes/release-notes.md

@@ -17,27 +17,70 @@ Firebolt continuously releases updates so that you can benefit from the latest a
 {: .note}
 Firebolt might roll out releases in phases. New features and changes may not yet be available to all accounts on the release date shown.
 
-## DB version 3.30
-**November 2023**
+## DB version 3.31
+**February 2024**
 
 * [New features](#new-features)
 * [Enhancements, changes, and new integrations](#enhancements-changes-and-new-integrations)
 * [Resolved issues](#resolved-issues)
 
 ### New features
 
-<!--- FIR-27590 ---> **New comparison operators**
+<!--- FIR-22307 --->**PG compliant division**
 
-[New comparison operators](../../sql_reference/operators.md#comparison) `IS DISTINCT FROM` and `IS NOT DISTINCT FROM` have been added.
+LQP2 has a new division operator that is PG compliant, by default.
+
+<!--- FIR-29179 --->**Prevents usage of new line delimeter for schema inference**
+
+An error will now occur if schema inference is used with the option “delimiter” set to something other than the default. 
 
 ### Enhancements, changes and new integrations
 
+<!--- FIR-27548 --->**Simplified table protobuf representation**
+
+Unique constraints in tables will be blocked for new accounts.
+
 <!--- FIR-27355 ---> **Support for nullable arrays**
 
-Support has been added to allow the [ANY_MATCH](../../sql_reference/functions-reference/Lambda/any-match.md) lambda function to work with nullable arrays.
+Support has been added to allow the [ANY_MATCH](../sql-reference/functions-reference/any-match.md) lambda function to work with nullable arrays.
+
+<!--- FIR-27799 --->**Updated AWS billing error message**
+
+The error message for an AWS billing issue on Engine Start was on Engine Start was changed to add more information and clarity.  
+
+<!--- FIR-28276 --->**New requirements updated for EXPLAIN**
+
+For `EXPLAIN` queries, we now allow only one of the following options at the same time: `ALL`, `LOGICAL`, `PHYSICAL`, `ANALYZE`.`EXPLAIN (ALL)` now returns the plans in multiple rows instead of multiple columns.
+
+<!--- FIR-29747 --->**Disabled Unix Time Functions**
+
+The following functions are not supported anymore:
+'from_unixtime'
+'to_unix_timestamp'
+'to_unix_time'
+
+<!--- FIR-29729 --->**Renamed spilled metrics columns**
+
+The columns `spilled_bytes_uncompressed` and `spilled_bytes_compressed` of `information_schema.query_history` have been replaced by a single column `spilled_bytes`(../sql_reference/information-schema/query-history-view.md). It contains the amount of data that was spilled to disk temporarily while executing the query.
+
+<!--- FIR-29536 --->**Aggregating index placement**
+
+Aggregating index is now placed in the same namespace as tables and views.
+
+<!--- FIR-29225 --->**Syntax and planner support for LATERAL scoping**
+
+LATERAL is now a reserved keyword (../Reference/reserved-words.md). It must now be used within double-quotes when using it as an object identifier.
 
 ### Resolved issues
 
-* Indirectly granted privileges have been removed from the `information_schema.object_privileges` view. 
+<!--- FIR-21152 --->Changed return for division by 0 from null to fail.
+
+<!--- FIR-18709 --->Updated error log for upload failure for clarity.
+
+<!--- FIR-29147 --->Fixed a bug in 'unnest' table function that occurred when not all of the 'unnest' columns were projected.
+
+<!--- FIR-28187 --->Changed the behavior of `split_part`(../sql_reference/functions-reference/string/split-part.md) when an empty string is used as delimiter.
+
+<!--- FIR-28623 --->Fixed a bug where floating point values `-0.0` and `+0.0`, as well as `-nan` and `+nan` were not considered equal in distributed queries.
 
-* Fixed an issue where `ARRAY_FIRST` and `ARRAY_FIRST_INDEX` returned an error if the given input was nullable.
+<!--- FIR-29759 --->TRY_CAST from TEXT to NUMERIC now works as expected: if the value cannot be parsed as NUMERIC it produces null.