diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/01_jdbc_rel_notes/jdbc_42.5.0.1_rel_notes.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/01_jdbc_rel_notes/jdbc_42.5.0.1_rel_notes.mdx index 94f1f75805a..a9bf30b1fab 100644 --- a/product_docs/docs/jdbc_connector/42.5.0.1/01_jdbc_rel_notes/jdbc_42.5.0.1_rel_notes.mdx +++ b/product_docs/docs/jdbc_connector/42.5.0.1/01_jdbc_rel_notes/jdbc_42.5.0.1_rel_notes.mdx @@ -7,11 +7,19 @@ The EDB JDBC connector provides connectivity between a Java application and an E New features, enhancements, bug fixes, and other changes in the EDB JDBC Connector 42.5.0.1 include: -| Type | Description | -| -------------- | ------------------------------------------------------------------------------- | -| Upstream Merge | Merged with the upstream community driver version 42.5.0. See the community [JDBC documentation](https://jdbc.postgresql.org/documentation/changelog.html#version_42.5.0) for details. | +| Type | Description | +| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Upstream Merge | Merged with the upstream community driver version 42.5.0. See the community [JDBC documentation](https://jdbc.postgresql.org/documentation/changelog.html#version_42.5.0) for details. | | Security Fix | CVE-2022-31197 - Fixes the SQL generated in PgResultSet.refresh() to escape column identifiers in order to prevent SQL injection. Previously, the column names for both key and data columns were copied as-is into the generated SQL. This allowed for a malicious table with column names that included a statment terminator to be parsed and executed as multiple separate commands. Also, this fix adds a new test class ResultSetRefreshTest to verify this change. | -| Change | Migrated build to Gradle. | +| Change | Migrated build to Gradle. | +| Enhancement | Added new `getServerName` connection property. If the value for `changeServerName` is set to `true`, it returns a value as `PostgreSQL`. The default value is `false`. | +| Enhancement | Added new `forceBinaryTransfer` connection property. If the value is set to `true`, forces the transfer of all binary types from the PostgreSQL server to the JDBC driver in their binary form. The default value is `false`. | + + + + + + diff --git a/product_docs/docs/jdbc_connector/42.5.0.1/05_using_the_advanced_server_jdbc_connector_with_java_applications/02_connecting_to_the_database/01_additional_connection_properties.mdx b/product_docs/docs/jdbc_connector/42.5.0.1/05_using_the_advanced_server_jdbc_connector_with_java_applications/02_connecting_to_the_database/01_additional_connection_properties.mdx index b3435090867..df47d129364 100644 --- a/product_docs/docs/jdbc_connector/42.5.0.1/05_using_the_advanced_server_jdbc_connector_with_java_applications/02_connecting_to_the_database/01_additional_connection_properties.mdx +++ b/product_docs/docs/jdbc_connector/42.5.0.1/05_using_the_advanced_server_jdbc_connector_with_java_applications/02_connecting_to_the_database/01_additional_connection_properties.mdx @@ -34,13 +34,15 @@ To specify additional connection properties in the URL, add a question mark and Some of the additional connection properties are shown in the following table. -| Name | Type | Description | -| --------------------- | ------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| user | String | The database user on whose behalf the connection is being made. | -| password | String | The database user’s password. | -| ssl | Boolean | Requests an authenticated, encrypted SSL connection. | -| charSet | String | The value of `charSet` determines the character set used for data sent to or received from the database. | -| prepareThreshold | Integer | The value of `prepareThreshold` determines the number of `PreparedStatement` executions required before switching to server-side prepared statements. The default is five. | -| loadBalanceHosts | Boolean | In default mode (disabled) hosts are connected in the given order. If enabled, hosts are chosen randomly from the set of suitable candidates. | +| Name | Type | Description | +| --------------------- | ------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| user | String | The database user on whose behalf the connection is being made. | +| password | String | The database user’s password. | +| ssl | Boolean | Requests an authenticated, encrypted SSL connection. | +| charSet | String | The value of `charSet` determines the character set used for data sent to or received from the database. | +| prepareThreshold | Integer | The value of `prepareThreshold` determines the number of `PreparedStatement` executions required before switching to server-side prepared statements. The default is five. | +| loadBalanceHosts | Boolean | In default mode (disabled) hosts are connected in the given order. If enabled, hosts are chosen randomly from the set of suitable candidates. | | targetServerType | String | Allows opening connections to only servers with the required state. The allowed values are `any`, `primary`, `secondary`, `preferSecondary`, and `preferSyncSecondary`. The primary/secondary distinction is currently done by observing if the server allows writes. The value `preferSecondary` tries to connect to secondaries if any are available, otherwise allows connecting to the primary. The EDB Postgres Advanced Server JDBC Connector supports `preferSyncSecondary`, which permits connection to only synchronous secondaries or the primary if there are no active synchronous secondaries. | -| skipQuotesOnReturning | Boolean | When set to `true`, column names from the `RETURNING` clause aren't quoted. This eliminates a case-sensitive comparison of the column name. When set to `false` (the default setting), column names are quoted. | +| skipQuotesOnReturning | Boolean | When set to `true`, column names from the `RETURNING` clause aren't quoted. This eliminates a case-sensitive comparison of the column name. When set to `false` (the default setting), column names are quoted. | +| changeServerName | Boolean | The `getServerName()` call in `PgConnection.java` returns `EnterpriseDB`. If `changeServerName` is set to `true`, it returns the value as `PostgreSQL`. The default value is `false`. | +| forceBinaryTransfer | Boolean | If the value is set to `true`, forces the transfer of all binary types from the PostgreSQL server to the JDBC driver in their binary form. The default value is `false`. | \ No newline at end of file diff --git a/product_docs/docs/migration_portal/4/04_mp_migrating_database/01_mp_schema_extraction/index.mdx b/product_docs/docs/migration_portal/4/04_mp_migrating_database/01_mp_schema_extraction/index.mdx index bd4ee2ce47f..7dedca250c0 100644 --- a/product_docs/docs/migration_portal/4/04_mp_migrating_database/01_mp_schema_extraction/index.mdx +++ b/product_docs/docs/migration_portal/4/04_mp_migrating_database/01_mp_schema_extraction/index.mdx @@ -1,6 +1,6 @@ --- title: "Performing a schema extraction" - +navTitle: "Schema extraction" legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. - "/edb-docs/d/edb-postgres-migration-portal/user-guides/user-guide/3.0.1/mp_schema_extraction.html" diff --git a/product_docs/docs/migration_portal/4/04_mp_migrating_database/02_mp_schema_assessment.mdx b/product_docs/docs/migration_portal/4/04_mp_migrating_database/02_mp_schema_assessment.mdx index d863672c634..ea94dd7ec05 100644 --- a/product_docs/docs/migration_portal/4/04_mp_migrating_database/02_mp_schema_assessment.mdx +++ b/product_docs/docs/migration_portal/4/04_mp_migrating_database/02_mp_schema_assessment.mdx @@ -1,6 +1,6 @@ --- title: "Performing a schema assessment" - +navTitle: "Schema assessment" legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. diff --git a/product_docs/docs/migration_portal/4/04_mp_migrating_database/03_mp_schema_migration.mdx b/product_docs/docs/migration_portal/4/04_mp_migrating_database/03_mp_schema_migration.mdx index 3164f16b214..10e35af503f 100644 --- a/product_docs/docs/migration_portal/4/04_mp_migrating_database/03_mp_schema_migration.mdx +++ b/product_docs/docs/migration_portal/4/04_mp_migrating_database/03_mp_schema_migration.mdx @@ -1,6 +1,6 @@ --- -title: "Schema migration" - +title: "Performing a schema migration" +navTitle: "Schema migration" legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key. @@ -9,191 +9,122 @@ legacyRedirectsGenerated: -After resolving errors in your schemas, you can use the schemas with a client application such as pgAdmin, Toad Edge, or the PSQL client. Or you can migrate the schema to an EDB Postgres Advanced Server. -You can migrate to any of these schemas: +After resolving errors in your schemas, you can migrate the schemas to an EDB Postgres Advanced Server cluster (i.e., instance). + +The Migration Portal provides guided steps for migrating your schemas to one of the following target database options: - Existing on-premises EDB Postgres Advanced Server - New on-premises EDB Postgres Advanced Server - EDB Postgres Advanced Server in the cloud +The first two options above lead to the creation of Data Definition Language (DDL) SQL files which can be used to perform an offline and manual loading of the schemas into the target database using a client application such as the psql client, pgAdmin, or Toad Edge. The third option above provides the ability to perform an online migration of the schemas to the target database by directly connecting to the target database. + ## Migrating to an existing on-premises EDB Postgres Advanced Server host You can migrate schemas to an existing on-premises EDB Postgres Advanced Server on Windows or Linux platforms. -### Migrate schemas on Windows - -1. Select **Existing on-premises EDB Postgres Postgres Advanced Server**. +1. Select **Existing on-premises EDB Postgres Postgres Advanced Server**. -1. Select one or more schemas to migrate to EDB Postgres Advanced Server. You can also expand a schema and select specific object types under each schema. +1. Select one or more schemas to migrate to EDB Postgres Advanced Server. You can also expand a schema and select specific object types under each schema. ![Schema and objects are selected](../images/schema_object_selection.png) - !!!Note + !!! Note If your schemas aren't 100% compatible, a banner appears. Complete the Contact Us form as needed. -1. To download the assessed schemas, select **Download SQL file**. - -1. Extract the downloaded zip file. The zip package consists of SQL files with DDLs for your selected schemas and objects. The DDLs are grouped in SQL files by project, schemas, or objects. +1. Select **Download SQL file**, to download the assessed schema. The zip package consists of SQL files with DDLs for your selected schemas and objects. The DDLs are grouped in SQL files by project, schemas, or objects. - | SQL file naming convention | Description | Example | + | File name | Description | Example | |------------------------------------------------|------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------| | *<ProjectName>* _ALL_OBJECTS.sql | A single consolidated file consisting of DDLs for all your selected schemas and objects. | **AllTestMigration_ALL_OBJECTS.sql** will consist of DDLs for all objects of schemas OE, SH, IX, and PM, and only selected objects of schema HR. | | *<SchemaName>* .sql | One or more files, each consisting of DDLs for selected objects in a particular schema. | **HR.sql** will consist of DDLs for all the selected objects of the HR schema. | | *<SchemaName>* _ *<ObjectType>* .sql | One or more files, each consisting of DDLs for a single selected object. | **HR_TABLE.sql** will consist of DDLs only for TABLE object of the HR schema. | -1. Select **Windows**. - -1. To import the schemas, run: +1. Import the schema into your target database: - - On CLI: + 1. Use the edb psql command line utility to connect to the EDB Postgres Advanced Server database from where the converted schema is to be migrated. - ```text - \i c:\users\...\.sql - ``` + 1. Create a new database: - - On cmd/shell: + ```SQL + CREATE DATABASE ; + ``` - ```text - edb-psql -f .sql - ``` - - !!! Note - You can alternatively use the `pgAdmin` client for the import. - -The converted schemas migrate to the target server. + 1. Connect to the new database using the following psql command: + ```SQL + \connect + ``` -### Migrate schemas on Linux + 1. Import the required SQL files into the new database using the following psql command: -You can migrate schemas to an existing on-premises EDB Postgres Advanced Server on Linux. + ```SQL + \i .sql + ``` -1. Select **Existing on-premises EDB Postgres Advanced Server**. - -1. Select one or more schemas to migrate to EDB Postgres Advanced Server. You can also expand a schema and select specific object types under each schema. - - ![Schema and objects are selected](../images/schema_object_selection.png) - -1. To download the assessed schemas, select **Download SQL file**. - -1. Extract the downloaded zip file. The zip package consists of SQL files with DDLs for your selected schemas and objects. The DDLs are grouped in SQL files by project, schemas, or objects. - - | SQL file naming convention | Description | Example | - |------------------------------------------------|------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------| - | *<ProjectName>* _ALL_OBJECTS.sql | A single consolidated file consisting of DDLs for all your selected schemas and objects. | **AllTestMigration_ALL_OBJECTS.sql** will consist of DDLs for all objects of schemas OE, SH, IX, and PM, and only selected objects of schema HR. | - | *<SchemaName>* .sql | One or more files, each consisting of DDLs for selected objects in a particular schema. | **HR.sql** will consist of DDLs for all the selected objects of the HR schema. | - | *<SchemaName>* _ *<ObjectType>* .sql | One or more files, each consisting of DDLs for a single selected object. | **HR_TABLE.sql** will consist of DDLs only for TABLE object of the HR schema. | - -1. Select **Linux**. - -1. To import the schemas, invoke the following `edb-psql` client commands: - - ```text - sudo su - enterprisedb - edb-psql edb - create database ; - \connect - \i .sql - ``` - - !!! Note - You can alternatively use the `pgAdmin` client for the import. + !!! Note + You can alternatively use the `pgAdmin` client for the import.1. Import the schema into your target database: The converted schemas migrate to the target server. + ## Migrating to a new on-premises EDB Postgres Advanced Server installation You can install new EDB Postgres Advanced Server on premises on Windows or Linux platforms and migrate the schemas. -### Migrate schemas on Windows +1. Select **New on-premises EDB Postgres Postgres Advanced Server**. -Migrate schemas to a new on-premises EDB Postgres Advanced Server on Windows. - -1. Select **New on-premises EDB Postgres Postgres Advanced Server**. - -1. Select one or more schemas to migrate to EDB Postgres Advanced Server. You can also expand a schema and select specific object types under each schema. +1. Select one or more schemas to migrate to EDB Postgres Advanced Server. You can also expand a schema and select specific object types under each schema. ![Schema and objects are selected](../images/schema_object_selection.png) -1. For the operating system, select **Windows**. - -1. Select **Download Windows installer**. - -1. For installation steps, select **EDB Postgres Advanced Server Installation Guide for Windows**. +1. Select your operating system. + + - For Windows: + + Select **Download Windows installer**. See [EDB Postgres Advanced Server installation for Windows](/epas/14/epas_inst_windows) for information on the installation procedure. -1. To download the assessed schemas, select **Download SQL file**. + - For Linux: + + Select either **Repository** or **More options** to install the EDB Postgres Advanced Server. See [EDB Postgres Advanced Server installation for Linux](/epas/14/epas_inst_linux/index.mdx) for information on the installation procedure. -1. Extract the downloaded zip file. The zip package consists of SQL files with DDLs for your selected schemas and objects. The DDLs are grouped in SQL files by project, schemas, or objects. +1. Select **Download SQL file**, to download the assessed schema. The zip package consists of SQL files with DDLs for your selected schemas and objects. The DDLs are grouped in SQL files by project, schemas, or objects. - | SQL file naming convention | Description | Example | + | File name | Description | Example | |------------------------------------------------|------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------| | *<ProjectName>* _ALL_OBJECTS.sql | A single consolidated file consisting of DDLs for all your selected schemas and objects. | **AllTestMigration_ALL_OBJECTS.sql** will consist of DDLs for all objects of schemas OE, SH, IX, and PM, and only selected objects of schema HR. | | *<SchemaName>* .sql | One or more files, each consisting of DDLs for selected objects in a particular schema. | **HR.sql** will consist of DDLs for all the selected objects of the HR schema. | | *<SchemaName>* _ *<ObjectType>* .sql | One or more files, each consisting of DDLs for a single selected object. | **HR_TABLE.sql** will consist of DDLs only for TABLE object of the HR schema. | -1. You can import schemas by running: - - - On CLI - - ```text - \i c:\users\...\.sql - ``` - - - On cmd/shell - - ```text - edb-psql -f .sql - ``` - - !!! Note - You can alternatively use the `pgAdmin` client for the import. - - -### Migrate schemas on Linux +1. Import the schema into your target database: -Migrate schemas to an on-premises EDB Postgres Advanced Server on Linux. + 1. Use the edb psql command line utility to connect to the EDB Postgres Advanced Server database from where the converted schema is to be migrated. -1. Select **New On-premises EDB Postgres Advanced Server**. + 1. Create a new database: -1. Select one or more schemas to migrate to EDB Postgres Advanced Server. You can also expand a schema and select specific object types under each schema. - - ![Schema and objects are selected](../images/schema_object_selection.png) + ```SQL + CREATE DATABASE ; + ``` -1. For the operating system, select **Linux**. + 1. Connect to the new database using the following psql command: -1. You can select one of the following options to install the EDB Postgres Advanced Server: + ```SQL + \connect + ``` - - Repository - - More options + 1. Import the required SQL files into the new database using the following psql command: -1. For information on the installation procedure, select **EDB Postgres Advanced Server Installation Guide** for Linux. + ```SQL + \i .sql + ``` -1. To download the assessed schemas, select **Download SQL file**. - -1. Extract the downloaded zip file. The zip package consists of SQL files with DDLs for your selected schemas and objects. The DDLs are grouped in SQL files by project, schemas, or objects. - - | SQL file naming convention | Description | Example | - |------------------------------------------------|------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------| - | *<ProjectName>* _ALL_OBJECTS.sql | A single consolidated file consisting of DDLs for all your selected schemas and objects. | **AllTestMigration_ALL_OBJECTS.sql** will consist of DDLs for all objects of schemas OE, SH, IX, and PM, and only selected objects of schema HR. | - | *<SchemaName>* .sql | One or more files, each consisting of DDLs for selected objects in a particular schema. | **HR.sql** will consist of DDLs for all the selected objects of the HR schema. | - | *<SchemaName>* _ *<ObjectType>* .sql | One or more files, each consisting of DDLs for a single selected object. | **HR_TABLE.sql** will consist of DDLs only for TABLE object of the HR schema. | - -1. To import the schemas, run: - - ```text - sudo su - enterprisedb - edb-psql edb - create database ; - \connect - \i .sql - ``` - - !!! Note - You can alternatively use the `pgAdmin` client for the import. + !!! Note + You can alternatively use the `pgAdmin` client for the import. The converted schemas migrate to the target server. @@ -201,32 +132,31 @@ The converted schemas migrate to the target server. Migrate schemas on EDB Postgres Advanced Server to the cloud. -1. Select **EDB Postgres Advanced Server on Cloud**. +1. Select **EDB Postgres Advanced Server on Cloud**. -1. Select one or more schemas to migrate to EDB Postgres Advanced Server. You can also expand a schema and select specific object types under each schema. +1. Select one or more schemas to migrate to EDB Postgres Advanced Server. You can also expand a schema and select specific object types under each schema. ![Schema and objects are selected](../images/schema_object_selection.png) -1. Select the cloud platform, for example, **BigAnimal**. +1. Select the cloud platform, for example, **BigAnimal**. -1. To launch a new cluster, select **Go to BigAnimal**. +1. To launch a new cluster, select **Go to BigAnimal**. Or, if you have an existing cluster running, select **Next**. !!! Note - See the [Big Animal](https://www.enterprisedb.com/edb-cloud) page for more information. + See the [BigAnimal](https://www.enterprisedb.com/edb-cloud) page for more information. -1. Enter the required connection details on the `Connect` page. +1. Enter the required connection details on the `Connect` page. ![Connecting to the cloud cluster](../images/mp_migrate_cloud_connection_updated.png) -1. To verify the connection details, select **Test Connection**. +1. To verify the connection details, select **Test Connection**. !!! Note You can select **Edit Connection** to make changes to the connection details and retest the connection details. -1. Once the connection is successful, select **Next**. - +1. Once the connection is successful, select **Next**. The converted schemas migrate to the target server. diff --git a/product_docs/docs/migration_portal/4/04_mp_migrating_database/04_mp_data_migration.mdx b/product_docs/docs/migration_portal/4/04_mp_migrating_database/04_mp_data_migration.mdx index 1a4dad7dbc1..83d172f77ba 100644 --- a/product_docs/docs/migration_portal/4/04_mp_migrating_database/04_mp_data_migration.mdx +++ b/product_docs/docs/migration_portal/4/04_mp_migrating_database/04_mp_data_migration.mdx @@ -1,6 +1,6 @@ --- -title: "Data migration" - +title: "Performing a data migration" +navTitle: "Data migration" legacyRedirectsGenerated: # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.