Merge pull request #6402 from EnterpriseDB/mig-handbook/epas17-updates

Migration Handbook: EPAS 17 updates

advocacy_docs/migrating/oracle/oracle_epas_comparison/app_devel_capabilities.mdx

@@ -40,6 +40,7 @@ EDB focuses on the most popular functions in packages. For some packages, not al
 | Package name   | Package description |
 |----------------|---------------------|
 | DBMS_ALERT     | Functions that allow asynchronous notification of database events by way of an alert. Using this package and triggers, an application can notify itself whenever values of interest in the database are changed. |
+| DBMS_ASSERT    | Provides a function that lets you sanitize and validate user input to help guard against SQL injections in applications. |
 | DBMS_AQ        | Database-integrated asynchronous message queuing provides a flexible mechanism for integrating applications across the enterprise by communicating activities and exchanging a variety of information payloads. |
 | DBMS_AQADM     | Provides procedures to create and manage queues and queue tables.|
 | DBMS_CRYPTO    | Provides functions to encrypt and decrypt stored data. |
@@ -57,6 +58,7 @@ EDB focuses on the most popular functions in packages. For some packages, not al
 | DBMS_SQL       | Permits the use of dynamic SQL in procedures to allow applications to run SQL statements with unknown parameters (such as table name) until runtime. |
 | DBMS_SESSION   | Functions with the ability to enable and disable roles. |
 | DBMS_UTILITY   | A collection of functions for getting information about various runtime operations and metadata from the database. |
+| DBMS_XMLDOM    | A collection of functions for creating DOM documents. |
 | HTF            | A collection of functions for generating HTML tags. |
 | HTP            | A collection of procedures for generating HTML tags. |
 | UTL_ENCODE     | Functions to perform Base64 encoding and decoding of data intended for transport between hosts. |

advocacy_docs/migrating/oracle/oracle_epas_comparison/non_relational_data.mdx

@@ -8,7 +8,7 @@ title: "Comparison of nonrelational data support"
 | Spatial/location/graph     | Yes                          | Yes                           |
 | JSON support               | Yes <br/> Text based         | Yes <br/> Text and high-performance binary based |
 | Key-value store            | NoSQL database               | Yes                           |
-| Support for XML namespaces, DOM, XQuery, SQL/XML, and XSLT | XML DB                        | No                            |
+| Support for XML namespaces, DOM, XQuery, SQL/XML, and XSLT | XML DB                       | Partial <br/> XML DOM support is provided via the DBMS_XMLDOM package                            |
 | Compression (tables, files, network, and backups) | Yes   | No <br/> Postgres performs compression of TOASTED rows |
 | Partitioning                       | Yes                  | Yes                           |
 | Hadoop integration         | Yes <br/> ETL via Data Integrator Application Adapter for Hadoop | Yes <br/> Real-time join with relational data with HDFS Foreign Data Wrapper |

advocacy_docs/migrating/oracle/oracle_epas_comparison/notable_differences.mdx

@@ -6,7 +6,7 @@ A number of differences between Oracle and EDB Postgres Advanced Server are eith
 
 | Oracle Enterprise            | EDB Postgres Advanced Server |
 |------------------------------|------------------------------|
-| MERGE                        | Yes <br/> EPAS 15 adds support for WHERE clauses to the UPDATE and INSERT of MERGE command to be more compatible with Oracle than community PostgreSQL. <br/> Additional Oracle compatible syntax planned for EPAS 16 | 
+| MERGE                        | Yes <br/> EPAS adds support for WHERE clauses to the UPDATE and INSERT of MERGE commands along with FORALL...MERGE commands for compatibility with Oracle beyond community PostgreSQL. | 
 | Advanced queuing             | Yes                          |
 | Nested procedures/functions  | Yes                          |
 | Pipelined functions          | No <br/> Pipelined functions are used for table functions. Table functions can be implemented in Postgres via SETOF returning functions. In Postgres, data is returned only after the function completes. |