4 Ways to Integrate EDB Postgres Using Popular Interfaces

June 22, 2018

Contributed by Eric McCormack

EnterpriseDB supports a wide array of connectors to integrate your application with EDB Postgres, and our Connectors team has been hard at work, just releasing our Connectors 10.0.2 update. This release made a host of enhancements to all four supported connectors. In this post, I’ll bring you up to speed on our supported connectors, their Oracle compatibility, and new features in this release. 

EDB Connectors are available for JDBC, .NET, ODBC, and OCI.
EDB’s JDBC Connector (a Type 4 Driver) provides connectivity between a Java application and EDB Postgres Advanced Server. The JDBC connector is written in Java and conforms to Sun's JDK architecture. The JDBC driver is our most mature and complete connector, containing most of the Oracle compatibility features and functionality of EDB Postgres. 

Our EDB Postgres Advanced Server .NET Connector provides connectivity between a .NET client application and EDB Postgres. Our .NET Connector is actually two connectors combined. The first is the original ADO.NET client. The second is the new Entity Framework. You might wonder what makes them different. The Entity Framework sits on top of ADO.NET provider and this makes it more of an ORM-based model.

Our EDB ODBC Connector provides connectivity between EDB Postgres Advanced Server and ODBC-compliant applications. We are investing a lot of resources into this connector with a goal to add even more Oracle compatibility features over time. Our team made great strides in our latest effort, and we have well-documented plans to improve upon these features with every release. 

Finally, we have our OCI Library. Applications that are written to use the Oracle Call Interface (OCI) may be recompiled using the EDB OCI connector to interact with an EDB Postgres Advanced Server database server. The latest release made a number of great improvements to this product, and this connector now delivers additional functionality requested by our customers. 

EDB Connectors and Oracle Compatibility
Our connectors provide great coverage for Oracle compatibility, as well, supporting these major features noted in the table below. One feature that I want to highlight is our support for Named Parameters. Not only are EDB Connectors compliant with Oracle, but this extension actually makes us more comprehensive than the JDBC driver you’ll find in the open source version of PostgreSQL.  

The support for Named Parameters gives programmers the ability to avoid entering values for columns that already have default parameters. They can just enter the stored document and then find the name of the parameters that are needed. This is truly a value-added and time-saving feature for our users.

What to Look For in the Connectors 10.0.2 Update
EDB Connectors team uses an agile development process and we manage our workflows through SCRUM methodology. We make quarterly releases, so look for our next Container update in late summer. We are hard at work and always innovating. If you have ideas to contribute or issues to report, reach out to support@enterprisedb.com. Until then, I have outlined all the details about what is new in our Connectors 10.0.2 update, below.

Connectors 10.0.2 Update Details

  • The EnterpriseDB JDBC Driver version has been merged with community driver from PGJDBC 42.1.4 to PGJDBC 42.2.2. More information about enhancements and fixes in the community driver can be found here. 
  • The EnterpriseDB .Net Driver version has been merged with new release of community Npgsql version 3.2.6. More information about this and other fixes in the community driver can be found here. 
  • EnterpriseDB ODBC Driver version 10.01.0000.01has been merge with community version: 10.01.0000. Contains upstream changes from psqlODBC 09.06.0300 to psqlODBC 10.01.0000. More information about this and other fixes in the community driver can be found here.

Eric McCormack is a Senior Connector Architect at EnterpriseDB.



Share this

Relevant Blogs

PostgreSQL VACUUM and ANALYZE Best Practice Tips

VACUUM and ANALYZE are the two most important PostgreSQL database maintenance operations.  A vacuum is used for recovering space occupied by “dead tuples” in a table. A dead tuple is...
January 27, 2023

JDBC logging using java.util.logging

Contributed by Eric McCormack The EnterpriseDB JDBC Driver supports the use of logging (or tracing) to help resolve issues with the JDBC Driver when is used in your application. The JDBC...
March 26, 2019