From fabb57ec7b1fcd5c0f9d584c2476efd32c2252d5 Mon Sep 17 00:00:00 2001 From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> Date: Tue, 5 Apr 2022 11:19:02 +0530 Subject: [PATCH 1/6] EC-2134 changes done Changes are done to version 5.0.7.1 --- .../5.0.7.1/13_using_a_ref_cursor_in_a_net_application.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/product_docs/docs/net_connector/5.0.7.1/13_using_a_ref_cursor_in_a_net_application.mdx b/product_docs/docs/net_connector/5.0.7.1/13_using_a_ref_cursor_in_a_net_application.mdx index fb6bd670b46..ae9cb924e81 100644 --- a/product_docs/docs/net_connector/5.0.7.1/13_using_a_ref_cursor_in_a_net_application.mdx +++ b/product_docs/docs/net_connector/5.0.7.1/13_using_a_ref_cursor_in_a_net_application.mdx @@ -24,14 +24,14 @@ The following sample code creates a stored procedure called `refcur_inout_callee ```Text CREATE OR REPLACE PROCEDURE - refcur_inout_callee(v_refcur IN OUT SYS_REFCURSOR) + refcur_inout_callee(v_refcur OUT SYS_REFCURSOR) IS BEGIN OPEN v_refcur FOR SELECT ename FROM emp; END; ``` -To use the above defined procedure from .NET code, you must specify the data type of the ref cursor being passed as an `IN` parameter, as shown in the above script. +To use the above defined procedure from .NET code, you must specify the data type of the ref cursor being passed as an `OUT` parameter, as shown in the above script. The following C# code uses the stored procedure to retrieve employee names from the `emp` table: @@ -62,7 +62,7 @@ namespace EDBRefCursor command.Parameters.Add(new EDBParameter("refCursor", EDBTypes.EDBDbType.Refcursor, 10, "refCursor", - ParameterDirection.InputOutput, false, 2, 2, + ParameterDirection.Output, false, 2, 2, System.Data.DataRowVersion.Current, null)); command.Prepare(); From f5d891de030b389f365c0dc86b5abdc6ef3e6512 Mon Sep 17 00:00:00 2001 From: Dee Dee Rothery <83650384+drothery-edb@users.noreply.github.com> Date: Tue, 5 Apr 2022 04:45:50 -0400 Subject: [PATCH 2/6] minor restructure --- .../5.0.7.1/13_using_a_ref_cursor_in_a_net_application.mdx | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/product_docs/docs/net_connector/5.0.7.1/13_using_a_ref_cursor_in_a_net_application.mdx b/product_docs/docs/net_connector/5.0.7.1/13_using_a_ref_cursor_in_a_net_application.mdx index ae9cb924e81..84a15042a38 100644 --- a/product_docs/docs/net_connector/5.0.7.1/13_using_a_ref_cursor_in_a_net_application.mdx +++ b/product_docs/docs/net_connector/5.0.7.1/13_using_a_ref_cursor_in_a_net_application.mdx @@ -20,7 +20,7 @@ Following is an example of a strongly-typed ref cursor: **Creating the Stored Procedure** -The following sample code creates a stored procedure called `refcur_inout_callee`. To create the sample procedure, invoke EDB-PSQL and connect to the Advanced Server host database. Enter the following SPL code at the command line: +The following sample code creates a stored procedure called `refcur_inout_callee`. It specifies the data type of the ref cursor being passed as an OUT parameter. To create the sample procedure, invoke EDB-PSQL and connect to the Advanced Server host database. Enter the following SPL code at the command line: ```Text CREATE OR REPLACE PROCEDURE @@ -31,8 +31,6 @@ BEGIN END; ``` -To use the above defined procedure from .NET code, you must specify the data type of the ref cursor being passed as an `OUT` parameter, as shown in the above script. - The following C# code uses the stored procedure to retrieve employee names from the `emp` table: ```Text From 5cb7258164c021581aa2465190aefecd1e9af17a Mon Sep 17 00:00:00 2001 From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> Date: Tue, 5 Apr 2022 16:05:44 +0530 Subject: [PATCH 3/6] Changes done to 4.1.6.1 version Changes done to 4.1.6.1 version --- .../13_using_a_ref_cursor_in_a_net_application.mdx | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/product_docs/docs/net_connector/4.1.6.1/13_using_a_ref_cursor_in_a_net_application.mdx b/product_docs/docs/net_connector/4.1.6.1/13_using_a_ref_cursor_in_a_net_application.mdx index 2ae728c0061..3a80106976b 100644 --- a/product_docs/docs/net_connector/4.1.6.1/13_using_a_ref_cursor_in_a_net_application.mdx +++ b/product_docs/docs/net_connector/4.1.6.1/13_using_a_ref_cursor_in_a_net_application.mdx @@ -23,19 +23,17 @@ Following is an example of a strongly-typed ref cursor: **Creating the Stored Procedure** -The following sample code creates a stored procedure called `refcur_inout_callee`. To create the sample procedure, invoke EDB-PSQL and connect to the Advanced Server host database. Enter the following SPL code at the command line: +The following sample code creates a stored procedure called `refcur_inout_callee`. It specifies the data type of the ref cursor being passed as an OUT parameter. To create the sample procedure, invoke EDB-PSQL and connect to the Advanced Server host database. Enter the following SPL code at the command line: ```Text CREATE OR REPLACE PROCEDURE - refcur_inout_callee(v_refcur IN OUT SYS_REFCURSOR) + refcur_inout_callee(v_refcur OUT SYS_REFCURSOR) IS BEGIN OPEN v_refcur FOR SELECT ename FROM emp; END; ``` -To use the above defined procedure from .NET code, you must specify the data type of the ref cursor being passed as an `IN` parameter, as shown in the above script. - The following C# code uses the stored procedure to retrieve employee names from the `emp` table: ```Text @@ -65,7 +63,7 @@ namespace EDBRefCursor command.Parameters.Add(new EDBParameter("refCursor", EDBTypes.EDBDbType.Refcursor, 10, "refCursor", - ParameterDirection.InputOutput, false, 2, 2, + ParameterDirection.Output, false, 2, 2, System.Data.DataRowVersion.Current, null)); command.Prepare(); From 33a90feac0b1271aa4469dc71c8f512aeb5290ef Mon Sep 17 00:00:00 2001 From: Betsy Gitelman <93718720+ebgitelman@users.noreply.github.com> Date: Tue, 5 Apr 2022 13:26:48 -0400 Subject: [PATCH 4/6] Completed editing pass of .NET connector --- .../5.0.7.1/01_release_notes.mdx | 6 +- .../5.0.7.1/02_requirements_overview.mdx | 8 +- ...advanced_server_net_connector_overview.mdx | 18 +-- ...ling_and_configuring_the_net_connector.mdx | 14 +- .../5.0.7.1/05_using_the_net_connector.mdx | 8 +- .../06_opening_a_database_connection.mdx | 84 +++++------- .../07_retrieving_database_records.mdx | 36 ++--- .../5.0.7.1/08_parameterized_queries.mdx | 18 +-- .../09_inserting_records_in_a_database.mdx | 16 +-- .../10_deleting_records_in_a_database.mdx | 14 +- ...red_procedures_in_your_net_application.mdx | 72 +++++----- .../5.0.7.1/12_using_advanced_queueing.mdx | 126 +++++++++--------- ...sing_a_ref_cursor_in_a_net_application.mdx | 20 +-- .../5.0.7.1/14_using_plugins.mdx | 18 +-- .../5.0.7.1/15_using_object_types.mdx | 20 ++- .../5.0.7.1/16_scram_compatibility.mdx | 4 +- ..._advanced_server_net_connector_logging.mdx | 10 +- .../5.0.7.1/18_api_reference.mdx | 2 +- .../docs/net_connector/5.0.7.1/index.mdx | 10 +- 19 files changed, 229 insertions(+), 275 deletions(-) diff --git a/product_docs/docs/net_connector/5.0.7.1/01_release_notes.mdx b/product_docs/docs/net_connector/5.0.7.1/01_release_notes.mdx index 099b1f5788d..1d5612d4406 100644 --- a/product_docs/docs/net_connector/5.0.7.1/01_release_notes.mdx +++ b/product_docs/docs/net_connector/5.0.7.1/01_release_notes.mdx @@ -1,12 +1,12 @@ --- -title: "Release Notes" +title: "Release notes" --- -The EDB .NET Connector provides connectivity between a .NET client application and an Advanced Server database server. +The EDB .NET Connector provides connectivity between a .NET client application and an EDB Postgres Advanced Server database server. New features, enhancements, bug fixes, and other changes in the EDB .NET Connector `5.0.7.1` include: | Type | Description | | -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Upstream Merge | Merged with the upstream Npgsql driver version 5.0.7. For more information about the merge updates, see . | +| Upstream merge | Merged with the upstream Npgsql driver version 5.0.7. For more information about the merge updates, see . | | Enhancement | Support for .NET 5.0 and .NET Core 3.1 (earlier available as .NET Core 3.0). | \ No newline at end of file diff --git a/product_docs/docs/net_connector/5.0.7.1/02_requirements_overview.mdx b/product_docs/docs/net_connector/5.0.7.1/02_requirements_overview.mdx index fd7d7eac9b1..fd547ac33b4 100644 --- a/product_docs/docs/net_connector/5.0.7.1/02_requirements_overview.mdx +++ b/product_docs/docs/net_connector/5.0.7.1/02_requirements_overview.mdx @@ -1,14 +1,12 @@ --- -title: "Requirements Overview" +title: "Requirements overview" --- -The following section details the supported platforms for the EDB .NET Connector. +These are the supported versions and platforms for the EDB .NET Connector. -## Supported Server Versions and Platforms - -The EDB .NET Connector is certified with Advanced Server version 9.6 and above. +The EDB .NET Connector is certified with EDB Postgres Advanced Server version 9.6 and above. The EDB .NET Connector graphical installers are supported on the following Windows platforms: diff --git a/product_docs/docs/net_connector/5.0.7.1/03_the_advanced_server_net_connector_overview.mdx b/product_docs/docs/net_connector/5.0.7.1/03_the_advanced_server_net_connector_overview.mdx index a067a4cca8b..4f4c23da601 100644 --- a/product_docs/docs/net_connector/5.0.7.1/03_the_advanced_server_net_connector_overview.mdx +++ b/product_docs/docs/net_connector/5.0.7.1/03_the_advanced_server_net_connector_overview.mdx @@ -1,35 +1,35 @@ --- -title: "The EDB .NET Connector - Overview" +title: "The EDB .NET Connector overview" --- -The EDB .NET Connector is a .NET data provider that allows a client application to connect to a database stored on an Advanced Server host. The .NET Connector accesses the data directly, allowing the client application optimal performance, a broad spectrum of functionality, and access to Advanced Server features. +The EDB .NET Connector is a .NET data provider that allows a client application to connect to a database stored on an EDB Postgres Advanced Server host. The .NET Connector accesses the data directly, allowing the client application optimal performance, a broad spectrum of functionality, and access to EDB Postgres Advanced Server features. -The .NET Connector supports following frameworks: +The .NET Connector supports the following frameworks: - .NET 5.0 - .NET Core 3.1 - .NET Standard 2.0 and 2.1 -## The .NET Class Hierarchy +## The .NET class hierarchy -The .NET Class Hierarchy contains a number of classes that you can use to create objects that control a connection to the Advanced Server database and manipulate the data stored on the server. The following are just a few of the most commonly used object classes: +The .NET class hierarchy contains classes that you can use to create objects that control a connection to the EDB Postgres Advanced Server database and manipulate the data stored on the server. The following are just a few of the most commonly used object classes. `EDBConnection` - The `EDBConnection` class represents a connection to Advanced Server. An `EDBConnection` object contains a `ConnectionString` that instructs the .NET client how to connect to an Advanced Server database. + The `EDBConnection` class represents a connection to EDB Postgres Advanced Server. An `EDBConnection` object contains a `ConnectionString` that instructs the .NET client how to connect to an EDB Postgres Advanced Server database. `EDBCommand` - An `EDBCommand` object contains an SQL command that the client will execute against Advanced Server. Before you can execute an `EDBCommand` object, you must link it to an `EDBConnection` object. + An `EDBCommand` object contains an SQL command that the client executes against EDB Postgres Advanced Server. Before you can execute an `EDBCommand` object, you must link it to an `EDBConnection` object. `EDBDataReader` - An `EDBDataReader` object provides a way to read an Advanced Server result set. You can use an `EDBDataReader` object to step through one row at a time, forward-only. + An `EDBDataReader` object provides a way to read an EDB Postgres Advanced Server result set. You can use an `EDBDataReader` object to step through one row at a time, forward only. `EDBDataAdapter` - An `EDBDataAdapter` object links a result set to the Advanced Server database. You can modify values and use the `EDBDataAdapter` class to update the data stored in an Advanced Server database. + An `EDBDataAdapter` object links a result set to the EDB Postgres Advanced Server database. You can modify values and use the `EDBDataAdapter` class to update the data stored in an EDB Postgres Advanced Server database. diff --git a/product_docs/docs/net_connector/5.0.7.1/04_installing_and_configuring_the_net_connector.mdx b/product_docs/docs/net_connector/5.0.7.1/04_installing_and_configuring_the_net_connector.mdx index f42a6e49a8a..492bc7a14ef 100644 --- a/product_docs/docs/net_connector/5.0.7.1/04_installing_and_configuring_the_net_connector.mdx +++ b/product_docs/docs/net_connector/5.0.7.1/04_installing_and_configuring_the_net_connector.mdx @@ -1,12 +1,10 @@ --- -title: "Installing and Configuring the .NET Connector" +title: "Installing and configuring the .NET Connector" --- -This chapter describes how to install and configure the EDB .NET Connector. - ## Installing the .NET Connector You can use the EDB .NET Connector Installer (available [from the EDB website](https://www.enterprisedb.com/software-downloads-postgres)) to add the .NET Connector to your system. After downloading the installer, right-click on the installer icon, and select `Run As Administrator` from the context menu. When prompted, select an installation language and click `OK` to continue to the `Setup` window. @@ -64,7 +62,7 @@ Please see the following environment-specific sections for information about con -### Referencing the Library Files +### Referencing the library files @@ -88,7 +86,7 @@ To import a namespace into a C# application, write: `using EnterpriseDB.EDBClient;` -### .NET Framework Setup +### .NET framework setup The following sections describe the setup for various .NET versions. @@ -216,7 +214,7 @@ Install dotnet-ef (using Command Prompt) `dotnet tool install --global dotnet-ef` -**Sample Project** +**Sample project** Create a new Console Application based on .NET 5.0 or NetCoreApp3.1 @@ -242,13 +240,13 @@ Command Prompt `Open Tools` → `Command Line` → `Developer Command Prompt` -**Database First Scenario** +**Database first scenario** Issue the following command to create Model Classes corresponding to all objects in the specified database: `dotnet ef dbcontext scaffold Host=;Database=;Username=;Password=;Port= EnterpriseDB.EDBClient.EntityFrameworkCore.PostgreSQL -o Models` -**Code First Scenario** +**Code first scenario** Add code for defining a DbContext and create, read, update & delete operations. diff --git a/product_docs/docs/net_connector/5.0.7.1/05_using_the_net_connector.mdx b/product_docs/docs/net_connector/5.0.7.1/05_using_the_net_connector.mdx index 6e089a1411d..dcdac30a376 100644 --- a/product_docs/docs/net_connector/5.0.7.1/05_using_the_net_connector.mdx +++ b/product_docs/docs/net_connector/5.0.7.1/05_using_the_net_connector.mdx @@ -5,11 +5,11 @@ title: "Using the .NET Connector" -The sections that follow provide examples that demonstrate using the EDB object classes that are provided by the EDB .NET Connector that allow a .NET application to connect to and interact with an Advanced Server database. +These examples show how you can use the EDB object classes that are provided by the EDB .NET Connector that allow a .NET application to connect to and interact with an EDB Postgres Advanced Server database. -To use the examples in this guide, place the .NET library files in the same directory as the compiled form of your application. All of the examples are written in C# and each is embedded in an ASP.NET page; the same logic and code would be applicable with other .NET applications (WinForm or console applications, for example). +To use these examples, place the .NET library files in the same directory as the compiled form of your application. All of these examples are written in C#, and each is embedded in an ASP.NET page. The same logic and code applies to other .NET applications (WinForm or console applications, for example). -Please create and save the following `web.config` file in the same directory as the sample code. The examples make use of the `DB_CONN_STRING` key from this configuration file to return a connection string from the Advanced Server host. +Create and save the following `web.config` file in the same directory as the sample code. The examples make use of the `DB_CONN_STRING` key from this configuration file to return a connection string from the EDB Postgres Advanced Server host. ```text @@ -21,4 +21,4 @@ Please create and save the following `web.config` file in the same directory as ``` -An Advanced Server connection string for an ASP.NET web application is stored in the `web.config` file. If you are writing an application that does not use ASP.NET, provide the connection information in an application configuration file (such as `app.config`). +An EDB Postgres Advanced Server connection string for an ASP.NET web application is stored in the `web.config` file. If you're writing an application that doesn't use ASP.NET, provide the connection information in an application configuration file such as `app.config`. diff --git a/product_docs/docs/net_connector/5.0.7.1/06_opening_a_database_connection.mdx b/product_docs/docs/net_connector/5.0.7.1/06_opening_a_database_connection.mdx index 3805da1a03d..a8baf0abb11 100644 --- a/product_docs/docs/net_connector/5.0.7.1/06_opening_a_database_connection.mdx +++ b/product_docs/docs/net_connector/5.0.7.1/06_opening_a_database_connection.mdx @@ -1,13 +1,13 @@ --- -title: "Opening a Database Connection" +title: "Opening a database connection" --- -An `EDBConnection` object is responsible for handling the communication between an instance of Advanced Server and a .NET application. Before you can access data stored in an Advanced Server database, you must create and open an `EDBConnection`. +An `EDBConnection` object is responsible for handling the communication between an instance of EDB Postgres Advanced Server and a .NET application. Before you can access data stored in an EDB Postgres Advanced Server database, you must create and open an `EDBConnection` object. -The examples that follow demonstrate the basic steps for connecting to an instance of Advanced Server. You must: +The examples that follow show the basic steps for connecting to an instance of Advanced Server. You must: 1. Import the namespace `EnterpriseDB.EDBClient`. 2. Create an instance of `EDBConnection`. @@ -16,20 +16,20 @@ The examples that follow demonstrate the basic steps for connecting to an instan -## Connection String Parameters +## Connection string parameters -A valid connection string should specify location and authentication information for an Advanced Server instance. You must provide the connection string before opening the connection. A connection string must contain: +A valid connection string specifies location and authentication information for an EDB Postgres Advanced Server instance. You must provide the connection string before opening the connection. A connection string must contain: - The name or IP address of the server -- The name of the Advanced Server database -- The name of an Advanced Server user +- The name of the EDB Postgres Advanced Server database +- The name of an EDB Postgres Advanced Server user - The password associated with that user -The following parameters may be included in the connection string: +You can include the following parameters in the connection string: `CommandTimeout` - `CommandTimeout` specifies the length of time (in seconds) to wait for a command to finish execution before throwing an exception. The default value is `20`. + `CommandTimeout` specifies the length of time (in seconds) to wait for a command to finish executing before throwing an exception. The default value is `20`. `ConnectionLifeTime` @@ -37,19 +37,19 @@ The following parameters may be included in the connection string: `Database` - Use the `Database` parameter to specify the name of the database to which the application should connect. If a database name is not specified, the database name will default to the name of the connecting user. + Use the `Database` parameter to specify the name of the database for the application to connect to. The default is the name of the connecting user. `Encoding` - The `Encoding` parameter is obsolete; the parameter always returns the string unicode, and silently ignores attempts to set it. + The `Encoding` parameter is obsolete. The parameter always returns the string `unicode` and silently ignores attempts to set it. `Integrated Security` - By default, `Integrated Security` is set to `false`, and Windows Integrated Security is disabled. Specify a value of `true` to use Windows Integrated Security. + Specify a value of `true` to use Windows Integrated Security. By default, `Integrated Security` is set to `false`, and Windows Integrated Security is disabled. `Load Role Based Tables` - Use `Load Role Based Tables` to load table OIDs based on role. This change only impacts the loading of table type OID, and not the composite type. The default value is `false`. Setting this parameter to `true` triggers the new functionality. + Use `Load Role Based Tables` to load table OIDs based on role. This change impacts only the loading of table type OID and not the composite type. Setting this parameter to `true` triggers the new functionality. The default value is `false`. `MaxPoolSize` @@ -57,23 +57,23 @@ The following parameters may be included in the connection string: `MinPoolSize` - `MinPoolSize` instructs `EDBConnection` to pre-allocate the specified number of connections with the server. The default value is `1`. + `MinPoolSize` instructs `EDBConnection` to preallocate the specified number of connections with the server. The default value is `1`. `Password` - When using clear text authentication, specify the password that will be used to establish a connection with the server. + When using clear text authentication, specify the password to use to establish a connection with the server. `Pooling` - By default, `Pooling` is set to `true` to enable connection pooling. Specify a value of `false` to disable connection pooling. + Specify a value of `false` to disable connection pooling. By default, `Pooling` is set to `true` to enable connection pooling. `Port` - The `Port` parameter specifies the port to which the application should connect. + The `Port` parameter specifies the port for the application to connect to. `Protocol` - The specific protocol version to use (instead of automatic); specify an integer value of 2 or 3. + The specific protocol version to use (instead of automatic). Specify an integer value of `2` or `3`. `SearchPath` @@ -81,27 +81,27 @@ The following parameters may be included in the connection string: `Server` - The name or IP address of the Advanced Server host. + The name or IP address of the EDB Postgres Advanced Server host. `SSL` - By default, `SSL` is set to `false`; specify a value of `true` to attempt a secure connection. + Specify a value of `true` to attempt a secure connection. By default, `SSL` is set to `false`. `sslmode` Use `sslmode` to specify an SSL connection control preference. `sslmode` can be: - `prefer` - Use SSL if possible. + `prefer` — Use SSL if possible. - `require` - Throw an exception if an SSL connection cannot be established. + `require` — Throw an exception if an SSL connection can't be established. - `allow` - Connect without SSL. This parameter is not supported. + `allow` — Connect without SSL. This parameter isn't supported. - `disable` - Do not attempt an SSL connection. This is the default behavior. + `disable` — Don't attempt an SSL connection. This is the default behavior. `SyncNotification` - Use the `SyncNotification` parameter to specify that `EDBDataprovider` should use synchronous notifications. The default value is `false`. + Use the `SyncNotification` parameter to specify for `EDBDataprovider` to use synchronous notifications. The default value is `false`. `Timeout` @@ -109,11 +109,11 @@ The following parameters may be included in the connection string: `User Id` - The `User Id` parameter specifies the user name that should be used for the connection. + The `User Id` parameter specifies the user name to use for the connection. -## Example - Opening a Database Connection using ASP.NET +## Example: Opening a database connection using ASP.NET -The following example demonstrates how to open a connection to an instance of Advanced Server and then close the connection. The connection is established using the credentials specified in the `DB_CONN_STRING` configuration parameter (see [Using the .Net Connector](05_using_the_net_connector/#using_the_net_connector) for an introduction to connection information and also see [Connection String Parameters](#connection-string-parameters) for connection parameters). +This example shows how to open a connection to an instance of EDB Postgres Advanced Server and then close the connection. The connection is established using the credentials specified in the `DB_CONN_STRING` configuration parameter. See [Using the .Net Connector](05_using_the_net_connector/#using_the_net_connector) for an introduction to connection information. Also see [Connection string parameters](#connection-string-parameters) for connection parameters. ```Text <% @ Page Language="C#" %> @@ -149,15 +149,11 @@ private void Page_Load(object sender, System.EventArgs e) ``` -If the connection is successful, a browser will display the following: +If the connection is successful, a message appears indicating that the connection opened successfully. -![Connection Opened Successfully](images/connection_opened_successfully.png) +## Example: Opening a database connection from a console application -Connection Opened Successfully - -## Example - Opening a Database Connection from a Console Application - -The following example opens a connection with an Advanced Server database using a console-based application. +This example opens a connection with an EDB Postgres Advanced Server database using a console-based application. Before writing the code for the console application, create an `app.config` file that stores the connection string to the database. Using a configuration file makes it convenient to update the connection string if the information changes. @@ -171,7 +167,7 @@ Before writing the code for the console application, create an `app.config` file ``` -Using your text editor of choice, enter the following code sample into a file: +Enter the following code sample into a file: ```Text using System; @@ -216,13 +212,11 @@ Save the file as `EDBConnection-Sample.cs` and compile it with the following com `csc /r:EnterpriseDB.EDBClient.dll /out:Console.exe EDBConnection-Sample.cs` -Compiling the sample should generate a `Console.exe` file; you can execute the sample code by entering `Console.exe`. When executed, the console should verify that the: - - `Connection Opened Successfully` +Compiling the sample generates a `Console.exe` file. You can execute the sample code by entering `Console.exe`. When executed, the console verifies that it opened successfully. -## Example - Opening a Database Connection from a Windows Form Application +## Example: Opening a database connection from a Windows form application -The following example demonstrates opening a database connection using a .NET WinForm application. To use the example, save the following code as `WinForm-Example.cs` in a directory that contains the library files. +This example opens a database connection using a .NET WinForm application. To use the example, save the following code as `WinForm-Example.cs` in a directory that contains the library files. ```Text using System; @@ -274,12 +268,8 @@ namespace EDBTestClient } ``` -Note that you must change the database connection string to point to the database that you want to connect to before compiling the file with the following command: +Change the database connection string to point to the database that you want to connect to. Then compile the file with the following command: `csc /r:EnterpriseDB.EDBClient.dll /out:WinForm.exe WinForm-Example.cs` -This command should generate a `WinForm.exe` file within the same folder that the executable was compiled under. Invoking the executable will display: - -![A successful connection](images/dialog.png) - -A successful connection +This command generates a `WinForm.exe` file in the same folder that the executable was compiled under. Invoking the executable displays a message that the connection was successful. diff --git a/product_docs/docs/net_connector/5.0.7.1/07_retrieving_database_records.mdx b/product_docs/docs/net_connector/5.0.7.1/07_retrieving_database_records.mdx index 82ce10458fc..08e0db54530 100644 --- a/product_docs/docs/net_connector/5.0.7.1/07_retrieving_database_records.mdx +++ b/product_docs/docs/net_connector/5.0.7.1/07_retrieving_database_records.mdx @@ -1,31 +1,31 @@ --- -title: "Retrieving Database Records" +title: "Retrieving database records" --- -You can use a `SELECT` statement to retrieve records from the database via a `SELECT` command. To execute a `SELECT` statement you must: +You can use a `SELECT` statement to retrieve records from the database using a `SELECT` command. To execute a `SELECT` statement you must: - Create and open a database connection. - Create an `EDBCommand` object that represents the `SELECT` statement. -- Execute the command with the `ExecuteReader()` method of the `EDBCommand` object returning a `EDBDataReader` -- Loop through the `EDBDataReader` displaying the results or binding the `EDBDataReader` to some control. +- Execute the command with the `ExecuteReader()` method of the `EDBCommand` object returning `EDBDataReader`. +- Loop through the `EDBDataReader`, displaying the results or binding the `EDBDataReader` to some control. An `EDBDataReader` object represents a forward-only and read-only stream of database records, presented one record at a time. To view a subsequent record in the stream, you must call the `Read()` method of the `EDBDataReader` object. The example that follows: -1. Imports the Advanced Server namespace: `EnterpriseDB.EDBClient` +1. Imports the EDB Postgres Advanced Server namespace `EnterpriseDB.EDBClient`. 2. Initializes an `EDBCommand` object with a `SELECT` statement. 3. Opens a connection to the database. 4. Executes the `EDBCommand` by calling the `ExecuteReader` method of the `EDBCommand` object. The results of the SQL statement are retrieved into an `EDBDataReader` object. -Loops through the contents of the `EDBDataReader` object to display the records returned by the query within a `WHILE` loop. +Loop through the contents of the `EDBDataReader` object to display the records returned by the query in a `WHILE` loop. -The `Read()` method advances to the next record (if a record exists) and returns `true` if a record exists, or `false` to indicate that the `EDBDataReader` has reached the end of the result set. +The `Read()` method advances to the next record (if a record exists) and returns `true` if a record exists. It returns `false` if `EDBDataReader` has reached the end of the result set. ```Text <% @ Page Language="C#" %> @@ -70,15 +70,9 @@ private void Page_Load(object sender, System.EventArgs e) ``` -To exercise the sample code, save the code in your default web root directory in a file named: +To exercise the sample code, save the code in your default web root directory in a file named `selectEmployees.aspx`. Then, to invoke the program, enter the following URL into a browser: `http://localhost/selectEmployees.aspx`. - `selectEmployees.aspx` - -To invoke the program, open a web-browser, and browse to: - - `http://localhost/selectEmployees.aspx` - -## Retrieving a Single Database Record +## Retrieving a single database record To retrieve a single result from a query, use the `ExecuteScalar()` method of the `EDBCommand` object. The `ExecuteScalar()` method returns the first value of the first column of the first row of the `DataSet` generated by the specified query. @@ -119,12 +113,8 @@ private void Page_Load(object sender, System.EventArgs e) ``` -Save the sample code in a file in a web root directory named: - - `selectscalar.aspx` - -To invoke the sample code, open a web-browser, and browse to: - - `http://localhost/selectScalar.aspx` +Save the sample code in a file named `selectscalar.aspx` in a web root directory. + +To invoke the sample code, enter the following in a browser: `http://localhost/selectScalar.aspx` -Please note that the sample includes an explicit conversion of the value returned by the `ExecuteScalar()` method. The `ExecuteScalar()` method returns an object; to view the object, you must convert it into an integer value by using the `Convert.ToInt32` method. +The sample includes an explicit conversion of the value returned by the `ExecuteScalar()` method. The `ExecuteScalar()` method returns an object. To view the object, you must convert it to an integer value by using the `Convert.ToInt32` method. diff --git a/product_docs/docs/net_connector/5.0.7.1/08_parameterized_queries.mdx b/product_docs/docs/net_connector/5.0.7.1/08_parameterized_queries.mdx index 07326d9113d..a6a3db44020 100644 --- a/product_docs/docs/net_connector/5.0.7.1/08_parameterized_queries.mdx +++ b/product_docs/docs/net_connector/5.0.7.1/08_parameterized_queries.mdx @@ -1,17 +1,17 @@ --- -title: "Parameterized Queries" +title: "Parameterized queries" --- -A `parameterized query` is a query with one or more parameter markers embedded in the SQL statement. Before executing a parameterized query, you must supply a value for each marker found in the text of the SQL statement. +A _parameterized query_ is a query with one or more parameter markers embedded in the SQL statement. Before executing a parameterized query, you must supply a value for each marker found in the text of the SQL statement. -Parameterized queries are useful when you don't know the complete text of a query at the time you write your code. For example, the value referenced in a `WHERE` clause may be calculated from user input. +Parameterized queries are useful when you don't know the complete text of a query when you write your code. For example, the value referenced in a `WHERE` clause can be calculated from user input. -As demonstrated in the following example, you must declare the data type of each parameter specified in the parameterized query by creating an `EDBParameter` object and adding that object to the command's parameter collection. Then, you must specify a `value` for each parameter by calling the parameter's `Value()` function. +As shown in the following example, you must declare the data type of each parameter specified in the parameterized query by creating an `EDBParameter` object and adding that object to the command's parameter collection. Then, you must specify a value for each parameter by calling the parameter's `Value()` function. -The example demonstrates use of a parameterized query with an `UPDATE` statement that increases an employee salary: +The example shows using a parameterized query with an `UPDATE` statement that increases an employee salary: ```text <% @ Page Language="C#" Debug="true"%> @@ -54,10 +54,6 @@ private void Page_Load(object sender, System.EventArgs e) ``` -Save the sample code in a file in a web root directory named: +Save the sample code in a file named `updateSalary.aspx` in a web root directory. - `updateSalary.aspx` - -To invoke the sample code, open a web-browser, and browse to: - - `http://localhost/updateSalary.aspx` +To invoke the sample code, enter the following in a browser: `http://localhost/updateSalary.aspx` diff --git a/product_docs/docs/net_connector/5.0.7.1/09_inserting_records_in_a_database.mdx b/product_docs/docs/net_connector/5.0.7.1/09_inserting_records_in_a_database.mdx index 0cc58f08906..a08fcf70866 100644 --- a/product_docs/docs/net_connector/5.0.7.1/09_inserting_records_in_a_database.mdx +++ b/product_docs/docs/net_connector/5.0.7.1/09_inserting_records_in_a_database.mdx @@ -1,15 +1,15 @@ --- -title: "Inserting Records in a Database" +title: "Inserting records in a database" --- -You can use the `ExecuteNonQuery()` method of `EDBCommand` to add records to a database stored on an Advanced Server host with an `INSERT` command. +You can use the `ExecuteNonQuery()` method of `EDBCommand` to add records to a database stored on an EDB Postgres Advanced Server host with an `INSERT` command. -In the example that follows, the `INSERT` command is stored in the variable cmd. The values prefixed with a colon (`:`) are placeholders for `EDBParameters` that are instantiated, assigned values, and then added to the `INSERT` command's parameter collection in the statements that follow. The `INSERT` command is executed by the `ExecuteNonQuery()` method of the `cmdInsert` object. +In the example that follows, the `INSERT` command is stored in the variable `cmd`. The values prefixed with a colon (`:`) are placeholders for `EDBParameters` that are instantiated, assigned values, and then added to the `INSERT` command's parameter collection in the statements that follow. The `INSERT` command is executed by the `ExecuteNonQuery()` method of the `cmdInsert` object. -The example adds a new employee to the `emp` table: +The example adds an employee to the `emp` table: ```Text <% @ Page Language="C#" Debug="true"%> @@ -59,10 +59,6 @@ private void Page_Load(object sender, System.EventArgs e) ``` -Save the sample code in a file in a web root directory named: +Save the sample code in a file named `insertEmployee.aspx` in a web root directory. - `insertEmployee.aspx` - -To invoke the sample code, open a web-browser, and browse to: - - `http://localhost/insertEmployee.aspx` +To invoke the sample code, enter the following in a browser: `http://localhost/insertEmployee.aspx` diff --git a/product_docs/docs/net_connector/5.0.7.1/10_deleting_records_in_a_database.mdx b/product_docs/docs/net_connector/5.0.7.1/10_deleting_records_in_a_database.mdx index 77ec759874a..ac5545aeb44 100644 --- a/product_docs/docs/net_connector/5.0.7.1/10_deleting_records_in_a_database.mdx +++ b/product_docs/docs/net_connector/5.0.7.1/10_deleting_records_in_a_database.mdx @@ -1,13 +1,13 @@ --- -title: "Deleting Records in a Database" +title: "Deleting records in a database" --- -You can use the `ExecuteNonQuery()` method of `EDBCommand` to delete records from a database stored on an Advanced Server host with a `DELETE` statement. +You can use the `ExecuteNonQuery()` method of `EDBCommand` to delete records from a database stored on an EDB Postgres Advanced Server host with a `DELETE` statement. -In the example that follows, the `DELETE` command is stored in the variable `strDeleteQuery`. The code passes the employee number to the Delete command (specified by: `EmpNo`). The command is then executed using the `ExecuteNonQuery()` method. The following example deletes the employee inserted in the previous example: +In the example that follows, the `DELETE` command is stored in the variable `strDeleteQuery`. The code passes the employee number to the `DELETE` command (specified by `EmpNo`). The command is then executed using the `ExecuteNonQuery()` method. ```text <% @ Page Language="C#" Debug="true"%> @@ -60,10 +60,6 @@ private void Page_Load(object sender, System.EventArgs e) ``` -Save the sample code in a file in a web root directory named: +Save the sample code in a file named `deleteEmployee.aspx` in a web root directory. - `deleteEmployee.aspx` - -To invoke the sample code, open a web-browser, and browse to: - - `http://localhost/deleteEmployee.aspx` +To invoke the sample code, enter the following in a browser: `http://localhost/deleteEmployee.aspx` diff --git a/product_docs/docs/net_connector/5.0.7.1/11_using_spl_stored_procedures_in_your_net_application.mdx b/product_docs/docs/net_connector/5.0.7.1/11_using_spl_stored_procedures_in_your_net_application.mdx index 35dc8f269f0..3950edbe6b6 100644 --- a/product_docs/docs/net_connector/5.0.7.1/11_using_spl_stored_procedures_in_your_net_application.mdx +++ b/product_docs/docs/net_connector/5.0.7.1/11_using_spl_stored_procedures_in_your_net_application.mdx @@ -1,5 +1,5 @@ --- -title: "Using SPL Stored Procedures in your .NET Application" +title: "Using SPL stored procedures in your .NET application" --- @@ -8,24 +8,24 @@ title: "Using SPL Stored Procedures in your .NET Application" You can include SQL statements in an application in two ways: - By adding the SQL statements directly in the .NET application code. -- By packaging the SQL statements in a stored procedure, and executing the stored procedure from the .NET application. +- By packaging the SQL statements in a stored procedure and executing the stored procedure from the .NET application. In some cases, a stored procedure can provide advantages over embedded SQL statements. Stored procedures support complex conditional and looping constructs that are difficult to duplicate with SQL statements embedded directly in an application. -You can also see a significant improvement in performance by using stored procedures; a stored procedure only needs to be parsed, compiled and optimized once on the server side, while a SQL statement that is included in an application may be parsed, compiled and optimized each time it is executed from a .NET application. +You can also see an improvement in performance by using stored procedures. A stored procedure needs to be parsed, compiled, and optimized only once on the server side. A SQL statement that's included in an application might be parsed, compiled, and optimized each time it's executed from a .NET application. To use a stored procedure in your .NET application you must: -1. Create an SPL stored procedure on the Advanced Server host. +1. Create an SPL stored procedure on the EDB Postgres Advanced Server host. 2. Import the `EnterpriseDB.EDBClient` namespace. 3. Pass the name of the stored procedure to the instance of the `EDBCommand`. 4. Change the `EDBCommand.CommandType` to `CommandType.StoredProcedure`. 5. `Prepare()` the command. 6. Execute the command. -## Example - Executing a Stored Procedure without Parameters +## Example: Executing a stored procedure without parameters -Our sample procedure prints the name of department 10; the procedure takes no parameters, and returns no parameters. To create the sample procedure, invoke EDB-PSQL and connect to the Advanced Server host database. Enter the following SPL code at the command line: +This sample procedure prints the name of department 10. The procedure takes no parameters and returns no parameters. To create the sample procedure, invoke EDB-PSQL and connect to the EDB Postgres Advanced Server host database. Enter the following SPL code at the command line: ```Text CREATE OR REPLACE PROCEDURE list_dept10 @@ -38,17 +38,17 @@ BEGIN END; ``` -When Advanced Server has validated the stored procedure it will echo `CREATE PROCEDURE`. +When EDB Postgres Advanced Server has validated the stored procedure, it echoes `CREATE PROCEDURE`. -**Using the EDBCommand Object to Execute a Stored Procedure** +### Using the EDBCommand object to execute a stored procedure -The `CommandType` property of the `EDBCommand` object is used to indicate the type of command being executed. The `CommandType` property is set to one of three possible `CommandType` enumeration values: +The `CommandType` property of the `EDBCommand` object indicates the type of command being executed. The `CommandType` property is set to one of three possible `CommandType` enumeration values: - Use the default `Text` value when passing a SQL string for execution. - Use the `StoredProcedure` value, passing the name of a stored procedure for execution. - Use the `TableDirect` value when passing a table name. This value passes back all records in the specified table. -The `CommandText` property must contain a SQL string, stored procedure name, or table name depending on the value of the `CommandType` property. +The `CommandText` property must contain a SQL string, stored procedure name, or table name, depending on the value of the `CommandType` property. The following example executes the stored procedure: @@ -93,17 +93,13 @@ private void Page_Load(object sender, System.EventArgs e) ``` -Save the sample code in a file in a web root directory named: +Save the sample code in a file named `storedProc.aspx` in a web root directory. - `storedProc.aspx` +To invoke the sample code, enter the following in a browser: `http://localhost/storedProc.aspx` -To invoke the sample code, open a web-browser, and browse to: +## Example: Executing a stored procedure with IN parameters - `http://localhost/storedProc.aspx` - -## Example - Executing a Stored Procedure with IN Parameters - -The following example demonstrates calling a stored procedure that includes `IN` parameters. To create the sample procedure, invoke `EDB-PSQL` and connect to the Advanced Server host database. Enter the following SPL code at the command line: +The following example shows calling a stored procedure that includes `IN` parameters. To create the sample procedure, invoke `EDB-PSQL` and connect to the EDB Postgres Advanced Server host database. Enter the following SPL code at the command line: ```Text CREATE OR REPLACE PROCEDURE @@ -130,13 +126,13 @@ BEGIN END; ``` -When Advanced Server has validated the stored procedure it wEDBTypes.EDBDbType.Floatill echo `CREATE PROCEDURE`. +When EDB Postgres Advanced Server has validated the stored procedure, it echoes `CREATE PROCEDURE`. -**Passing Input Values to a Stored Procedure** +### Passing input values to a stored procedure -Calling a stored procedure that contains parameters is very similar to executing a stored procedure without parameters. The major difference is that when calling a parameterized stored procedure you must use the `EDBParameter` collection of the `EDBCommand` object. When the `EDBParameter` is added to the `EDBCommand` collection, properties such as `ParameterName`, `DbType`, `Direction`, `Size`, and `Value` are set. +Calling a stored procedure that contains parameters is similar to executing a stored procedure without parameters. The major difference is that, when calling a parameterized stored procedure, you must use the `EDBParameter` collection of the `EDBCommand` object. When the `EDBParameter` is added to the `EDBCommand` collection, properties such as `ParameterName`, `DbType`, `Direction`, `Size`, and `Value` are set. -The following example demonstrates the process of executing a parameterized stored procedure from a C#. +The following example shows the process of executing a parameterized stored procedure from a C# script. ```Text <% @ Page Language="C#" Debug="true"%> @@ -223,13 +219,9 @@ private void Page_Load(object sender, System.EventArgs e) ``` -Save the sample code in a file in a web root directory named: - - `storedProcInParam.aspx` - -To invoke the sample code, open a web-browser, and browse to: +Save the sample code in a file named `storedProcInParam.aspx` in a web root directory. - `http://localhost/storedProcInParam.aspx` +To invoke the sample code, enter the following in a browser: `http://localhost/storedProcInParam.aspx` In the example, the body of the `Page_Load` method declares and instantiates an `EDBConnection` object. The sample then creates an `EDBCommand` object with the properties needed to execute the stored procedure. @@ -241,19 +233,19 @@ EDBCommand cmdStoredProc = new EDBCommand cmdStoredProc.CommandType = CommandType.StoredProcedure; ``` -It assigns a value to each parameter before passing them to the `EMP_INSERT` stored procedure +It assigns a value to each parameter before passing them to the `EMP_INSERT` stored procedure. The `Prepare()` method prepares the statement before calling the `ExecuteNonQuery()` method. -The `ExecuteNonQuery` method of the `EDBCommand` object executes the stored procedure. After the stored procedure has executed, a test record is inserted into the `emp` table and the values inserted are displayed on the webpage. +The `ExecuteNonQuery` method of the `EDBCommand` object executes the stored procedure. After the stored procedure executes, a test record is inserted into the `emp` table, and the values inserted are displayed on the webpage. -## Example - Executing a Stored Procedure with IN, OUT, and INOUT Parameters +## Example: Executing a stored procedure with IN, OUT, and INOUT parameters -The previous example demonstrated how to pass `IN` parameters to a stored procedure; the following examples demonstrate how to pass `IN` values and return `OUT` values from a stored procedure. +The previous example demonstrated how to pass `IN` parameters to a stored procedure. The following examples show how to pass `IN` values and return `OUT` values from a stored procedure. -**Creating the Stored Procedure** +### Creating the stored procedure -The following stored procedure passes the department number, and returns the corresponding location and department name. To create the sample procedure, open the EDB-PSQL command line, and connect to the Advanced Server host database. Enter the following SPL code at the command line: +The following stored procedure passes the department number and returns the corresponding location and department name. To create the sample procedure, open the EDB-PSQL command line, and connect to the EDB Postgres Advanced Server host database. Enter the following SPL code at the command line: ```Text CREATE OR REPLACE PROCEDURE @@ -279,18 +271,18 @@ BEGIN END; ``` -When Advanced Server has validated the stored procedure it will echo `CREATE PROCEDURE`. +When EDB Postgres Advanced Server has validated the stored procedure, it echoes `CREATE PROCEDURE`. -**Receiving Output Values from a Stored Procedure** +### Receiving output values from a stored procedure -When retrieving values from `OUT` parameters you must explicitly specify the direction of out parameters as `Output`. You can retrieve the values from `Output` parameters in two ways: +When retrieving values from `OUT` parameters, you must explicitly specify the direction of those parameters as `Output`. You can retrieve the values from `Output` parameters in two ways: - Call the `ExecuteReader` method of the `EDBCommand` and explicitly loop through the returned `EDBDataReader`, searching for the values of `OUT` parameters. - Call the `ExecuteNonQuery` method of `EDBCommand` and explicitly get the value of a declared `Output` parameter by calling that `EDBParameter` value property. -In each method, you must declare each parameter, indicating the `direction` of the parameter (`ParameterDirection.Input`, `ParameterDirection.Output` or `ParameterDirection.InputOutput`). Before invoking the procedure, you must provide a value for each `IN` and `INOUT` parameter. After the procedure returns, you may retrieve the `OUT` and `INOUT` parameter values from the `command.Parameters[]` array. +In each method, you must declare each parameter, indicating the direction of the parameter (`ParameterDirection.Input`, `ParameterDirection.Output`, or `ParameterDirection.InputOutput`). Before invoking the procedure, you must provide a value for each `IN` and `INOUT` parameter. After the procedure returns, you can retrieve the `OUT` and `INOUT` parameter values from the `command.Parameters[]` array. -The following code listing demonstrates using the `ExecuteReader` method to retrieve a result set: +The following code shows using the `ExecuteReader` method to retrieve a result set: ```Text <% @ Page Language="C#" Debug="true"%> @@ -357,7 +349,7 @@ private void Page_Load(object sender, System.EventArgs e) ``` -The following code listing demonstrates using the `ExecuteNonQuery` method to retrieve a result set: +The following code shows using the `ExecuteNonQuery` method to retrieve a result set: ```Text <% @ Page Language="C#" Debug="true"%> diff --git a/product_docs/docs/net_connector/5.0.7.1/12_using_advanced_queueing.mdx b/product_docs/docs/net_connector/5.0.7.1/12_using_advanced_queueing.mdx index 55f968b9117..1cc0b985b04 100644 --- a/product_docs/docs/net_connector/5.0.7.1/12_using_advanced_queueing.mdx +++ b/product_docs/docs/net_connector/5.0.7.1/12_using_advanced_queueing.mdx @@ -1,33 +1,33 @@ --- -title: "Using Advanced Queueing" +title: "Using advanced queueing" --- -EDB Postgres Advanced Server Advanced Queueing provides message queueing and message processing for the Advanced Server database. User-defined messages are stored in a queue; a collection of queues is stored in a queue table. You should first create a queue table before creating a queue that is dependent on it. +EDB Postgres Advanced Server advanced queueing provides message queueing and message processing for the EDB Postgres Advanced Server database. User-defined messages are stored in a queue. A collection of queues is stored in a queue table. Create a queue table before creating a queue that depends on it. -On the server side, procedures in the `DBMS_AQADM` package create and manage message queues and queue tables. Use the `DBMS_AQ` package to add or remove messages from a queue, or register or unregister a PL/SQL callback procedure. For more information about `DBMS_AQ` and `DBMS_AQADM`, click [here](https://www.enterprisedb.com/docs/en/11.0/EPAS_BIP_Guide_v11/Database_Compatibility_for_Oracle_Developers_Built-in_Package_Guide.1.14.html#pID0E01HG0HA). +On the server side, procedures in the `DBMS_AQADM` package create and manage message queues and queue tables. Use the `DBMS_AQ` package to add or remove messages from a queue or register or unregister a PL/SQL callback procedure. For more information about `DBMS_AQ` and `DBMS_AQADM`, see [DBMS_AQ](../../epas/11/epas_compat_bip_guide/03_built-in_packages/02_dbms_aq/#pID0E01HG0HA). -On the client side, application uses EDB.NET driver to enqueue/dequeue message. +On the client side, the application uses the EDB.NET driver to enqueue and dequeue messages. -## Enqueueing or Dequeueing a Message +## Enqueueing or dequeueing a message -For more information about using Advanced Servers Advanced Queueing functionality, see the [Database Compatibility for Oracle Developers Built-in Package Guide](/epas/latest/). +For more information about using EDB Postgres Advanced Server's advanced queueing functionality, see the [Database Compatibility for Oracle Developers Built-in Package Guide](/epas/latest/epas_compat_bip_guide/). -### Server-Side Setup +### Server-side setup -To use Advanced Queueing functionality on your .NET application, you must first create a user defined type, queue table, and queue, and then start the queue on the database server. Invoke EDB-PSQL and connect to the Advanced Server host database. Use the following SPL commands at the command line: +To use advanced queueing functionality on your .NET application, you must first create a user-defined type, queue table, and queue, and then start the queue on the database server. Invoke EDB-PSQL and connect to the EDB Postgres Advanced Server host database. Use the following SPL commands at the command line: -**Creating a User-defined Type** +**Creating a user-defined type** -To specify a RAW data type, you should create a user-defined type. The following example demonstrates creating a user-defined type named as `myxml`. +To specify a RAW data type, create a user-defined type. The following example shows creating a user-defined type named as `myxml`. `CREATE TYPE myxml AS (value XML)`; -**Creating the Queue Table** +**Creating the queue table** -A queue table can hold multiple queues with the same payload type. The following example demonstrates creating a table named `MSG_QUEUE_TABLE`. +A queue table can hold multiple queues with the same payload type. The following example shows creating a table named `MSG_QUEUE_TABLE`. ```Text EXEC DBMS_AQADM.CREATE_QUEUE_TABLE @@ -37,9 +37,9 @@ EXEC DBMS_AQADM.CREATE_QUEUE_TABLE END; ``` -**Creating the Queue** +**Creating the queue** -The following example demonstrates creating a queue named `MSG_QUEUE` within the table `MSG_QUEUE_TABLE`. +The following example shows creating a queue named `MSG_QUEUE` in the table `MSG_QUEUE_TABLE`. ```Text BEGIN @@ -47,7 +47,7 @@ DBMS_AQADM.CREATE_QUEUE ( queue_name => 'MSG_QUEUE', queue_table => 'MSG_QUEUE_T END; ``` -**Starting the Queue** +**Starting the queue** Once the queue is created, invoke the following SPL code at the command line to start a queue in the EDB database. @@ -58,11 +58,11 @@ DBMS_AQADM.START_QUEUE END; ``` -### Client-side Example +### Client-side example -Once you have created a user-defined type, followed by queue table and queue, start the queue. Then, you can enqueue or dequeue a message using EDB .Net drivers. +Once you've created a user-defined type, followed by queue table and queue, start the queue. Then, you can enqueue or dequeue a message using EDB .Net drivers. -**Enqueue a message:** +**Enqueue a message** To enqueue a message on your .NET application, you must: @@ -71,10 +71,10 @@ To enqueue a message on your .NET application, you must: 3. Create the enqueue message and define a payload. 4. Call the `queue.Enqueue` method. -The following code listing demonstrates using the `queue.Enqueue` method: +The following code shows using the `queue.Enqueue` method: !!! Note - The following code creates the message and serializes it. This is just an example code and is not going to compile if copied as it is. It is the responsibility of the user to serialize the message as XML. + The following code creates the message and serializes it. This is just an example code and won't compile if copied as it is. You must serialize the message as XML. ```Text using EnterpriseDB.EDBClient; @@ -197,7 +197,7 @@ To dequeue a message on your .NET application, you must: 3. Call the `queue.Dequeue` method. !!! Note - The following code creates the message and serializes it. This is just an example code and is not going to compile if copied as it is. It is the responsibility of the user to serialize the message as XML. + The following code creates the message and serializes it. This is just an example code and won't compile if copied as it is. You must serialize the message as XML. ```Text using System; @@ -359,7 +359,7 @@ namespace DequeueXML } ``` -## EDBAQ Classes +## EDBAQ classes The following EDBAQ classes are used in this application: @@ -367,9 +367,9 @@ The following EDBAQ classes are used in this application: The `EDBAQDequeueMode` class lists all the dequeuer modes available. -| **Value** | **Description** | +| Value | Description | | ------------- | ------------------------------------------------------------- | -| Browse | Read the message without locking. | +| Browse | Reads the message without locking. | | Locked | Reads and gets a write lock on the message. | | Remove | Deletes the message after reading. This is the default value. | | Remove_NoData | Confirms receipt of the message. | @@ -378,36 +378,36 @@ The `EDBAQDequeueMode` class lists all the dequeuer modes available. The `EDBAQDequeueOptions` class lists the options available when dequeuing a message. -| **Property** | **Description** | +| Property | Description | | -------------- | ------------------------------------------------------------------------------------------------------------------------------ | | ConsumerName | The name of the consumer for which to dequeue the message. | -| DequeueMode | This is set from EDBAQDequeueMode. It represents the locking behavior linked with the dequeue option. | -| Navigation | This is set from EDBAQNavigationMode. It represents the position of the message that will be fetched. | -| Visibility | This is set from EDBAQVisibility. It represents whether the new message is dequeued or not as part of the current transaction. | +| DequeueMode | This is set from `EDBAQDequeueMode`. It represents the locking behavior linked with the dequeue option. | +| Navigation | This is set from `EDBAQNavigationMode`. It represents the position of the message to fetch. | +| Visibility | This is set from `EDBAQVisibility`. It represents whether the new message is dequeued as part of the current transaction. | | Wait | The wait time for a message as per the search criteria. | | Msgid | The message identifier. | | Correlation | The correlation identifier. | | DeqCondition | The dequeuer condition. It is a Boolean expression. | -| Transformation | The transformation that will be applied before dequeuing the message. | +| Transformation | The transformation to apply before dequeuing the message. | | DeliveryMode | The delivery mode of the dequeued message. | **EDBAQEnqueueOptions** The `EDBAQEnqueueOptions` class lists the options available when enqueuing a message. -| **Property** | **Description** | +| Property | Description | | ----------------- | ------------------------------------------------------------------------------------------------------------------------------ | -| Visibility | This is set from EDBAQVisibility. It represents whether the new message is enqueued or not as part of the current transaction. | +| Visibility | This is set from `EDBAQVisibility`. It represents whether the new message is enqueued as part of the current transaction. | | RelativeMsgid | The relative message identifier. | -| SequenceDeviation | The sequence when the message should be dequeued. | -| Transformation | The transformation that will be applied before enqueuing the message. | +| SequenceDeviation | The sequence when to dequeue the message. | +| Transformation | The transformation to apply before enqueuing the message. | | DeliveryMode | The delivery mode of the enqueued message. | **EDBAQMessage** -The `EDBAQMessage` class lists a message to be enqueued/dequeued. +The `EDBAQMessage` class lists a message to enqueue/dequeue. -| **Property** | **Description** | +| Property | Description | | ------------ | -------------------------------- | | Payload | The actual message to be queued. | | MessageId | The ID of the queued message. | @@ -416,17 +416,17 @@ The `EDBAQMessage` class lists a message to be enqueued/dequeued. The `EDBAQMessageProperties` lists the message properties available. -| **Property** | **Description** | +| Property | Description | | ---------------- | --------------------------------------------------------------------------------------------- | | Priority | The priority of the message. | -| Delay | The duration post which the message is available for dequeuing. This is specified in seconds. | -| Expiration | The duration for which the message is available for dequeuing. This is specified in seconds. | +| Delay | The duration post which the message is available for dequeuing, in seconds. | +| Expiration | The duration for which the message is available for dequeuing, in seconds. | | Correlation | The correlation identifier. | | Attempts | The number of attempts taken to dequeue the message. | -| RecipientList | The receipients list that overthrows the default queue subscribers. | -| ExceptionQueue | The name of the queue where the unprocessed messages should be moved. | +| RecipientList | The recipients list that overthrows the default queue subscribers. | +| ExceptionQueue | The name of the queue to move the unprocessed messages to. | | EnqueueTime | The time when the message was enqueued. | -| State | The state of the message while dequeue. | +| State | The state of the message while dequeued. | | OriginalMsgid | The message identifier in the last queue. | | TransactionGroup | The transaction group for the dequeued messages. | | DeliveryMode | The delivery mode of the dequeued message. | @@ -435,28 +435,28 @@ The `EDBAQMessageProperties` lists the message properties available. The `EDBAQMessageState` class represents the state of the message during dequeue. -| **Value** | **Description** | -| --------- | ---------------------------------------------------------- | -| Expired | The message is moved to the exception queue. | -| Processed | The message is processed and kept. | -| Ready | The message is ready to be processed. | -| Waiting | The message is in waiting state. The delay is not reached. | +| Value | Description | +| --------- | --------------------------------------------------------- | +| Expired | The message is moved to the exception queue. | +| Processed | The message is processed and kept. | +| Ready | The message is ready to be processed. | +| Waiting | The message is in waiting state. The delay isn't reached. | **EDBAQMessageType** The `EDBAQMessageType` class represents the types for payload. -| **Value** | **Description** | +| Value | Description | | --------- | ------------------------------------------------------------------------------------- | -| Raw | The raw message type.

Note: Currently, this payload type is not supported. | +| Raw | The raw message type.

Note: Currently, this payload type isn't supported. | | UDT | The user defined type message. | -| XML | The XML type message.

Note: Currently, this payload type is not supported. | +| XML | The XML type message.

Note: Currently, this payload type isn't supported. | **EDBAQNavigationMode** The `EDBAQNavigationMode` class represents the different types of navigation modes available. -| **Value** | **Description** | +| Value | Description | | ---------------- | ------------------------------------------------------------------ | | First_Message | Returns the first available message that matches the search terms. | | Next_Message | Returns the next available message that matches the search items. | @@ -466,25 +466,25 @@ The `EDBAQNavigationMode` class represents the different types of navigation mod The `EDBAQQueue` class represents a SQL statement to execute `DMBS_AQ` functionality on a PostgreSQL database. -| **Property** | **Description** | +| Property | Description | | ----------------- | --------------------------------------------------------------------------------------------- | -| Connection | The connection to be used. | -| Name | The name of the queue. | -| MessageType | The message type that is enqueued/dequeued from this queue. For example EDBAQMessageType.Udt. | -| UdtTypeName | The user defined type name of the message type. | -| EnqueueOptions | The enqueue options to be used. | -| DequeuOptions | The dequeue options to be used. | -| MessageProperties | The message properties to be used. | +| Connection | The connection to use | +| Name | The name of the queue | +| MessageType | The message type that's enqueued/dequeued from this queue, for example `EDBAQMessageType.Udt` | +| UdtTypeName | The user-defined type name of the message type | +| EnqueueOptions | The enqueue options to use | +| DequeuOptions | The dequeue options to use | +| MessageProperties | The message properties to use | **EDBAQVisibility** The `EDBAQVisibility` class represents the visibility options available. -| **Value** | **Description** | +| Value | Description | | --------- | ----------------------------------------------------------- | -| Immediate | The enqueue/dequeue is not part of the ongoing transaction. | +| Immediate | The enqueue/dequeue isn't part of the ongoing transaction. | | On_Commit | The enqueue/dequeue is part of the current transaction. | !!! Note - - To review the default options for the above parameters, click [here](https://www.enterprisedb.com/docs/en/11.0/EPAS_BIP_Guide_v11/Database_Compatibility_for_Oracle_Developers_Built-in_Package_Guide.1.14.html#pID0E01HG0HA/). - - EDB Advanced Queueing functionality uses user-defined types for calling enqueue/dequeue operations. `Server Compatibility Mode=NoTypeLoading` cannot be used with Advanced Queueing because `NoTypeLoading` will not load any user-defined types. +- To review the default options for these parameters, see [DBMS_AQ](../../epas/11/epas_compat_bip_guide/03_built-in_packages/02_dbms_aq/#pID0E01HG0HA/). + - EDB advanced queueing functionality uses user-defined types for calling enqueue/dequeue operations. `Server Compatibility Mode=NoTypeLoading` can't be used with advanced queueing because `NoTypeLoading` doesn't load any user-defined types. diff --git a/product_docs/docs/net_connector/5.0.7.1/13_using_a_ref_cursor_in_a_net_application.mdx b/product_docs/docs/net_connector/5.0.7.1/13_using_a_ref_cursor_in_a_net_application.mdx index fb6bd670b46..c7ec5910423 100644 --- a/product_docs/docs/net_connector/5.0.7.1/13_using_a_ref_cursor_in_a_net_application.mdx +++ b/product_docs/docs/net_connector/5.0.7.1/13_using_a_ref_cursor_in_a_net_application.mdx @@ -1,26 +1,26 @@ --- -title: "Using a Ref Cursor in a .NET Application" +title: "Using a ref cursor in a .NET application" --- -A `ref cursor` is a cursor variable that contains a pointer to a query result set. The result set is determined by the execution of the `OPEN FOR` statement using the cursor variable. A cursor variable is not tied to a particular query like a static cursor. The same cursor variable may be opened a number of times with the `OPEN FOR` statement containing different queries and each time, a new result set will be created for that query and made available via the cursor variable. There are two ways to declare a cursor variable: +A `ref cursor` is a cursor variable that contains a pointer to a query result set. The result set is determined by executing the `OPEN FOR` statement using the cursor variable. A cursor variable isn't tied to a particular query like a static cursor. You can open the same cursor variable a number of times with the `OPEN FOR` statement containing different queries and each time. A new result set is created for that query and made available by way of the cursor variable. You can declare a cursor variable in two ways: -- Use the `SYS_REFCURSOR` built-in data type to declare a weakly-typed ref cursor. -- Define a strongly-typed ref cursor that declares a variable of that type. +- Use the `SYS_REFCURSOR` built-in data type to declare a weakly typed ref cursor. +- Define a strongly typed ref cursor that declares a variable of that type. -`SYS_REFCURSOR` is a ref cursor type that allows any result set to be associated with it. This is known as a weakly-typed ref cursor. The following example is a declaration of a weakly-typed ref cursor: +`SYS_REFCURSOR` is a ref cursor type that allows any result set to be associated with it. This is known as a weakly typed ref cursor. The following example is a declaration of a weakly typed ref cursor: `name SYS_REFCURSOR`; -Following is an example of a strongly-typed ref cursor: +Following is an example of a strongly typed ref cursor: `TYPE IS REF CURSOR RETURN emp%ROWTYPE`; -**Creating the Stored Procedure** +## Creating the stored procedure -The following sample code creates a stored procedure called `refcur_inout_callee`. To create the sample procedure, invoke EDB-PSQL and connect to the Advanced Server host database. Enter the following SPL code at the command line: +The following sample code creates a stored procedure called `refcur_inout_callee`. To create the sample procedure, invoke EDB-PSQL and connect to the EDB Postgres Advanced Server host database. Enter the following SPL code at the command line: ```Text CREATE OR REPLACE PROCEDURE @@ -31,7 +31,7 @@ BEGIN END; ``` -To use the above defined procedure from .NET code, you must specify the data type of the ref cursor being passed as an `IN` parameter, as shown in the above script. +To use this procedure from .NET code, you must specify the data type of the ref cursor being passed as an `IN` parameter, as shown in the script. The following C# code uses the stored procedure to retrieve employee names from the `emp` table: @@ -104,4 +104,4 @@ for(int i = 0;i < fc; i++) } ``` -Please note that you must bind the `EDBDbType.RefCursor` type in `EDBParameter()` if you are using a ref cursor parameter. +You must bind the `EDBDbType.RefCursor` type in `EDBParameter()` if you're using a ref cursor parameter. diff --git a/product_docs/docs/net_connector/5.0.7.1/14_using_plugins.mdx b/product_docs/docs/net_connector/5.0.7.1/14_using_plugins.mdx index f71a1dbfd7c..f4b10818555 100644 --- a/product_docs/docs/net_connector/5.0.7.1/14_using_plugins.mdx +++ b/product_docs/docs/net_connector/5.0.7.1/14_using_plugins.mdx @@ -1,11 +1,11 @@ --- -title: "Using Plugins" +title: "Using plugins" --- -EDB .Net driver plugins are introduced to support the enhanced capabilities for different data types, which are otherwise not available in .Net. The different plugins available support: +EDB .Net driver plugins support the enhanced capabilities for different data types that are otherwise not available in .Net. The different plugins available support: - GeoJSON - Json.NET @@ -14,11 +14,11 @@ EDB .Net driver plugins are introduced to support the enhanced capabilities for - NodaTime - Rawpostgis -The plugins support the use of spatial, data/time and Json types. The following sections detail the supported frameworks and data provider installation path for these plugins. +The plugins support the use of spatial, data/time, and JSON types. The following are the supported frameworks and data provider installation path for these plugins. ## GeoJSON -If you are using the GeoJSON plugin on .NET Standard 2.0, the data provider installation path is: +If you're using the GeoJSON plugin on .NET Standard 2.0, the data provider installation path is: `C:\Program Files\edb\dotnet\plugins\GeoJSON\netstandard2.0` @@ -30,7 +30,7 @@ For detailed information about using the GeoJSON plugin, see the [Npgsql documen ## Json.NET -If you are using the Json.NET plugin on .NET Standard 2.0, the data provider installation path is: +If you're using the Json.NET plugin on .NET Standard 2.0, the data provider installation path is: `C:\Program Files\edb\dotnet\plugins\Json.NET\netstandard2.0` @@ -42,7 +42,7 @@ For detailed information about using the Json.NET plugin, see the [Npgsql docume ## LegacyPostGIS -If you are using the LegacyPostGIS plugin on .Net Standard 2.0, the data provider installation path is: +If you're using the LegacyPostGIS plugin on .Net Standard 2.0, the data provider installation path is: `C:\Program Files\edb\dotnet\plugins\LegacyPostgis\netstandard2.0` @@ -54,7 +54,7 @@ For detailed information about using the LegacyPostGIS plugin, see the [Npgsql d ## NetTopologySuite -If you are using the NetTopologySuite plugin on .Net Standard 2.0, the data provider installation path is: +If you're using the NetTopologySuite plugin on .Net Standard 2.0, the data provider installation path is: `C:\Program Files\edb\dotnet\plugins\NetTopologySuite\netstandard2.0` @@ -66,7 +66,7 @@ For detailed information about using the NetTopologySuite type plugin, see the [ ## NodaTime -If you are using the NodaTime plugin on .Net Standard 2.0, the data provider installation path is: +If you're using the NodaTime plugin on .Net Standard 2.0, the data provider installation path is: `C:\Program Files\edb\dotnet\plugins\NodaTime\netstandard2.0` @@ -78,7 +78,7 @@ For detailed information about using the NodaTime plugin, see the [Npgsql docume ## RawPostGIS -If you are using the RawPostGIS type plugin on .Net Standard 2.0, the data provider installation path is: +If you're using the RawPostGIS type plugin on .Net Standard 2.0, the data provider installation path is: `C:\Program\Files\edb\dotnet\plugins\RawPostGis\netstandard2.0` diff --git a/product_docs/docs/net_connector/5.0.7.1/15_using_object_types.mdx b/product_docs/docs/net_connector/5.0.7.1/15_using_object_types.mdx index f9c5feb00ac..909897b0e27 100644 --- a/product_docs/docs/net_connector/5.0.7.1/15_using_object_types.mdx +++ b/product_docs/docs/net_connector/5.0.7.1/15_using_object_types.mdx @@ -1,21 +1,19 @@ --- -title: "Using Object Types in .NET" +title: "Using object types in .NET" --- -The SQL `CREATE TYPE` command is used to create a user-defined `object type`, which is stored in the Advanced Server database. +The SQL `CREATE TYPE` command creates a user-defined object type, which is stored in the EDB Postgres Advanced Server database. -These user-defined types can then be referenced within SPL procedures, SPL functions, and .NET programs. +You can then reference these user-defined types in SPL procedures, SPL functions, and .NET programs. -The basic object type is created with the `CREATE TYPE AS OBJECT` command along with optional usage of the `CREATE TYPE BODY` command. +The basic object type is created with the `CREATE TYPE AS OBJECT` command with optional use of the `CREATE TYPE BODY` command. -An example that demonstrates using an object type is shown in the following section. +## Using an object type -## Using an Object Type - -To use an object type, you must first create the object type in the Advanced Server database. Object type `addr_object_type` defines the attributes of an address: +To use an object type, you must first create the object type in the EDB Postgres Advanced Server database. Object type `addr_object_type` defines the attributes of an address: ```text CREATE OR REPLACE TYPE addr_object_type AS OBJECT @@ -27,7 +25,7 @@ CREATE OR REPLACE TYPE addr_object_type AS OBJECT ); ``` -Object type `emp_obj_typ` defines the attributes of an employee. Note that one of these attributes is object type `ADDR_OBJECT_TYPE` as previously described. The object type body contains a method that displays the employee information: +Object type `emp_obj_typ` defines the attributes of an employee. One of these attributes is object type `ADDR_OBJECT_TYPE`, as previously described. The object type body contains a method that displays the employee information: ```text CREATE OR REPLACE TYPE emp_obj_typ AS OBJECT @@ -128,7 +126,7 @@ namespace ObjectTypesSample } ``` -The following .NET types are defined to map to the types in Advanced Server: +The following .NET types are defined to map to the types in EDB Postgres Advanced Server: ```text public class addr_object_type @@ -147,7 +145,7 @@ public class emp_obj_typ } ``` -A call to `EDBConnection.GlobalTypeMapper.MapComposite` maps the .NET type to the Advanced Server types: +A call to `EDBConnection.GlobalTypeMapper.MapComposite` maps the .NET type to the EDB Postgres Advanced Server types: ```text EDBConnection.GlobalTypeMapper.MapComposite("enterprisedb.addr_object_type"); diff --git a/product_docs/docs/net_connector/5.0.7.1/16_scram_compatibility.mdx b/product_docs/docs/net_connector/5.0.7.1/16_scram_compatibility.mdx index 18c71d2fa63..886739de0ae 100644 --- a/product_docs/docs/net_connector/5.0.7.1/16_scram_compatibility.mdx +++ b/product_docs/docs/net_connector/5.0.7.1/16_scram_compatibility.mdx @@ -1,5 +1,5 @@ --- -title: "Scram Compatibility" +title: "Scram compatibility" legacyRedirects: - "/edb-docs/d/edb-postgres-net-connector/user-guides/net-guide/4.1.6.1/security_and_encryption.html" @@ -7,4 +7,4 @@ legacyRedirects: -The EDB .NET driver provides SCRAM-SHA-256 support for Advanced Server version 10 and above. This support is available from EDB .NET 4.0.2.1 release onwards. +The EDB .NET driver provides SCRAM-SHA-256 support for EDB Postgres Advanced Server version 10 and above. This support is available from EDB .NET 4.0.2.1 release onwards. diff --git a/product_docs/docs/net_connector/5.0.7.1/17_advanced_server_net_connector_logging.mdx b/product_docs/docs/net_connector/5.0.7.1/17_advanced_server_net_connector_logging.mdx index cfe7cedec8a..90c8a7c7122 100644 --- a/product_docs/docs/net_connector/5.0.7.1/17_advanced_server_net_connector_logging.mdx +++ b/product_docs/docs/net_connector/5.0.7.1/17_advanced_server_net_connector_logging.mdx @@ -1,5 +1,5 @@ --- -title: "EDB .NET Connector Logging" +title: "EDB .NET Connector logging" --- @@ -7,9 +7,9 @@ title: "EDB .NET Connector Logging" EDB .NET Connector supports the use of logging to help resolve issues with the .NET Connector when used in your application. The connector uses classes in the `EnterpriseDB.EDBClient.Logging` namespace for logging. -**Console Logging to Standard Error** +## Console logging to standard error -`EnterpriseDB.EDBClient.Logging.ConsoleLoggingProvider` is a class that outputs error messages to `STDERR`. To use this class, include the following line in your application before using any of the Advanced Server .NET Connector APIs. +`EnterpriseDB.EDBClient.Logging.ConsoleLoggingProvider` is a class that outputs error messages to `STDERR`. To use this class, include the following line in your application before using any of the EDB Postgres Advanced Server .NET Connector APIs. `EnterpriseDB.EDBClient.Logging.EDBLogManager.Provider = new EnterpriseDB.EDBClient.Logging.ConsoleLoggingProvider(EDBLogLevel.Debug, true, true);` @@ -22,9 +22,9 @@ The following log levels are available: - Error - Fatal -**Writing a Custom Logger** +## Writing a custom logger -If the console logging provider does not fulfill your requirements, you can write a custom logger by implementing the `EnterpriseDB.EDBClient.Logging.IEDBLoggingProvider` interface, and extending the `EnterpriseDB.EDBClient.Logging.EDBLogger` class, for instance, writing your logs to a file. The following is a simple example of how to write a custom logger: +If the console logging provider doesn't meet your needs, you can write a custom logger by implementing the `EnterpriseDB.EDBClient.Logging.IEDBLoggingProvider` interface and extending the `EnterpriseDB.EDBClient.Logging.EDBLogger` class, for instance, writing your logs to a file. The following is a simple example of how to write a custom logger: ```text public class MyLoggingProvider : IEDBLoggingProvider diff --git a/product_docs/docs/net_connector/5.0.7.1/18_api_reference.mdx b/product_docs/docs/net_connector/5.0.7.1/18_api_reference.mdx index a9427a4252d..53050c37952 100644 --- a/product_docs/docs/net_connector/5.0.7.1/18_api_reference.mdx +++ b/product_docs/docs/net_connector/5.0.7.1/18_api_reference.mdx @@ -1,5 +1,5 @@ --- -title: "API Reference" +title: "API reference" --- diff --git a/product_docs/docs/net_connector/5.0.7.1/index.mdx b/product_docs/docs/net_connector/5.0.7.1/index.mdx index c4b46db933a..c64ca407201 100644 --- a/product_docs/docs/net_connector/5.0.7.1/index.mdx +++ b/product_docs/docs/net_connector/5.0.7.1/index.mdx @@ -4,13 +4,13 @@ directoryDefaults: description: "EDB .NET Connector Version 5.0.7.1 Documentation and release notes." --- -The EDB .NET Connector distributed with EDB Postgres Advanced Server (Advanced Server) provides connectivity between a .NET client application and an Advanced Server database server. This guide provides installation instructions, usage instructions, and examples that demonstrate the functionality of the EDB .NET Connector: +The EDB .NET Connector distributed with EDB Postgres Advanced Server provides connectivity between a .NET client application and an EDB Postgres Advanced Server database server. You can: -- How to connect to an instance of Advanced Server. -- How to retrieve information from an Advanced Server database. -- How to update information stored on an Advanced Server database. +- Connect to an instance of EDB Postgres Advanced Server. +- Retrieve information from an EDB Postgres Advanced Server database. +- Update information stored on an EDB Postgres Advanced Server database. -This document assumes that you have a solid working knowledge of both C# and .NET. The EDB .NET Connector functionality is built on the core functionality of the Npgsql open source project. The *Npgsql User's Manual* is available [online](http://www.npgsql.org/doc/index.html). +To understand these examples, you need a solid working knowledge of C# and .NET. The EDB .NET Connector functionality is built on the core functionality of the Npgsql open source project. For details, see the [Npgsql User Guide](http://www.npgsql.org/doc/index.html).
From 5ad1fc0f63785a630d6f5930b359b71e33b5b13a Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Tue, 5 Apr 2022 14:46:05 -0400 Subject: [PATCH 5/6] small nit --- .../docs/net_connector/5.0.7.1/02_requirements_overview.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/net_connector/5.0.7.1/02_requirements_overview.mdx b/product_docs/docs/net_connector/5.0.7.1/02_requirements_overview.mdx index fd547ac33b4..7409d0b49be 100644 --- a/product_docs/docs/net_connector/5.0.7.1/02_requirements_overview.mdx +++ b/product_docs/docs/net_connector/5.0.7.1/02_requirements_overview.mdx @@ -6,7 +6,7 @@ title: "Requirements overview" These are the supported versions and platforms for the EDB .NET Connector. -The EDB .NET Connector is certified with EDB Postgres Advanced Server version 9.6 and above. +The EDB .NET Connector is certified with EDB Postgres Advanced Server version 10 and later. The EDB .NET Connector graphical installers are supported on the following Windows platforms: From f8fb6b5c76892e5d73ae0a0fc0da8443b6eab540 Mon Sep 17 00:00:00 2001 From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> Date: Wed, 6 Apr 2022 10:41:18 +0530 Subject: [PATCH 6/6] PEMESC-386 added to 8.4 release notes PEMESC-386 added to 8.4 release notes --- product_docs/docs/pem/8/pem_rel_notes/04_840_rel_notes.mdx | 1 + 1 file changed, 1 insertion(+) diff --git a/product_docs/docs/pem/8/pem_rel_notes/04_840_rel_notes.mdx b/product_docs/docs/pem/8/pem_rel_notes/04_840_rel_notes.mdx index b76dbf8a7c5..918f07884f2 100644 --- a/product_docs/docs/pem/8/pem_rel_notes/04_840_rel_notes.mdx +++ b/product_docs/docs/pem/8/pem_rel_notes/04_840_rel_notes.mdx @@ -21,3 +21,4 @@ New features, enhancements, bug fixes, and other changes in PEM 8.4.0 include: | Bug Fix | Probe error for Postgres Extended 14. | PEM-4356 | | Bug Fix | PEM agent not gathering data after upgrade. [Support Ticket #78679] | PEM-4430 | | Bug Fix | Added an option in preferences to change the line ending of the email body content from LF(Line Feed) to CRLF (Carriage Return Line Feed). This fixes missing alert body content in email notifications. [Support Ticket #833910] | PEM-1832 | +| Bug Fix | Fixed pg_isready time out issue in configure script [Support Ticket #RT75651] | PEMESC-386 | \ No newline at end of file