KB-31085: Connecting Elipse E3 to PostgreSQL.

How can I connect Elipse E3 to a PostgreSQL database? Does it have native support to this database, or do I need to perform any extra procedures to do so?

PostgreSQL is a powerful, open source object-relational database system with over 35 years of active development that has earned it a strong reputation for reliability, feature robustness, and performance. It supports both SQL (relational) and JSON (non-relational) querying, and is the fourth most popular database in the world.

From Elipse E3 version 6.5 on, the supervisory has featured native support to PostgreSQL databases, in addition to Access, SQLServer, MySQL and Oracle databases. For previous versions of Elipse E3, you can use the procedure described below.

If you’re using any Elipse E3 version prior to 6.5, you can also connect to the PostgreSQL database. However, you won’t have native support to it, and therefore need to connect to it via OBDC. To do so, you must be sure you have its connection string (you can check it at  www.connectionstrings.com for more information), and then add it to a script. In this case, you will not be able to use any E3 database objects, such as Historic, Storage, and E3Query.

Due to these limitations, whenever you use this database, the E3 application will usually record all data with a database with native support in older versions  (Access, SQLServer, or Oracle), and then the database will periodically execute a direct command to export all data to PostgreSQL (in this case, you can use a  StoredProcedure that does this automatically).