PostgresDAC - Direct Access Components for PostgreSQL and EnterpriseDB/Heroku Postgres


Direct access components for PostgreSQL and EnterpriseDB/Heroku Postgres
Powerful component suite for Delphi/C++Builder and PostgreSQL 7.x, 8.x, 9.x and EnterpriseDB/Heroku Postgres. It allows you to create Delphi/C++Builder applications with direct access to PostgreSQL and EnterpriseDB/Heroku Postgres DB without BDE and ODBC.

Top 10 reasons to use PostgresDAC

  • PostgresDAC is a royalty-free product;
  • support of Delphi 5-7, C++Builder 5-6, Borland Developer Studio 2005-2006 Win32 edition, Turbo Delphi 2006, Turbo C++ 2006, CodeGear RAD Studio 2007 (both Delphi 2007 and C++Builder 2007) Win32 Edition, CodeGear Delphi and C++Builder 2009 (Tiburon), Embarcadero RAD Studio 2010 (both Delphi 2010 and C++Builder 2010), Embarcadero RAD Studio XE (Delphi XE and C++Builder XE), Embarcadero RAD Studio XE2 (Delphi XE2 and C++Builder XE2), Embarcadero RAD Studio XE3 (Delphi XE3 and C++Builder XE3), Embarcadero RAD Studio XE4 (Delphi XE4 and C++Builder XE4), Embarcadero RAD Studio XE5 (Delphi XE5 and C++Builder XE5), Embarcadero RAD Studio XE6 (Delphi XE6 and C++Builder XE6), Embarcadero RAD Studio XE7 (Delphi XE7 and C++Builder XE7), Embarcadero RAD Studio XE8 (Delphi XE8 and C++Builder XE8), Embarcadero RAD Studio 10 Seattle (Delphi 10 Seattle and C++Builder 10 Seattle), Embarcadero RAD Studio 10.1 Berlin (Delphi 10.1 Berlin and C++Builder 10.1 Berlin), Embarcadero RAD Studio 10.2 Tokyo (Delphi 10.2 Tokyo and C++Builder 10.2 Tokyo);
  • only 300-400 Kb are added to your .exe file;
  • full compatibility with all the existing data-aware controls and report designers;
  • full support of the BLOB fields;
  • PostgresDAC is the only product fully support PostgreSQL native dump file format;
  • detailed help system and a lot of various demo applications;
  • and much more. Please find more details in the online documentation.

PostgresDAC Components:

TPSQLDataBase provides discrete control over a connection to a single database in a database application.
Use TPSQLDataBase when a database application requires any of the following control over a database connection:
  • Persistent database connections;
  • Customized database server logins;
  • Transaction control.
TPSQLTable encapsulates a database table.
Use TPSQLTable to access data in a single database table. TPSQLTable provides direct access to every record and field in an underlying database table. TPSQLTable can also work with a subset of records within a database table using ranges and filters.
At design time, create, delete, update, or rename the database table connected to a TPSQLTable by right-clicking on the TPSQLTable and using the pop-up menu.
TPSQLQuery encapsulates a dataset with a result set that is based on an SQL statement.
Use TPSQLQuery to access one or more PostgreSQL tables in a database using SQL statements. TPSQLQuery component is useful because it can:
  • Access more than one table at a time (called a "join" in SQL).
  • Automatically access a subset of rows and columns in its underlying table(s), rather than always returning all rows and columns.
TPSQLUpdateSQL applies updates on behalf of queries or stored procedures that can't post updates directly.
Use a TPSQLUpdateSQL object to provide SQL statements used to update read-only datasets represented by TPSQLQuery component. A dataset is read-only either by design or circumstance. If a dataset is read-only by design, the application itself does not provide a user interface for updating data, but may institute a programmatic scheme behind the scenes. If a dataset is read-only by circumstance, it indicates that the PostgreSQL returned a read-only result set. This usually happens for queries made against multiple tables. Such queries are, by SQL-92 definitions, read-only.
TPSQLBatchExecute component can execute SQL scripts containing more than one SQL statement.
TPSQLMacroQuery is the decessor of TPSQLQuery component and supports all of its properties, methods, events, and functionalities.
TPSQLMonitor monitors dynamic SQL passed to the PostgreSQL server.
TPSQLDump is a component for backing up a PostgreSQL database. It makes consistent backups even if the database is being used concurrently. TPSQLDump does not block other users accessing the database (readers or writers).
Dumps can be output in script or archive file formats. The script files are in plain-text format and contain the SQL commands required to reconstruct the database to the state it was in at the time it was saved. To restore these scripts, use TPSQLBatchExecute, in example. They can be used to reconstruct the database even on other machines and other architectures, with some modifications even on other SQL database products.
The alternative archive file formats that are meant to be used with TPSQLRestore or native pg_restore utility to rebuild the database, and they also allow to be selective about what is restored, or even to reorder the items prior to being restored. The archive files are also designed to be portable across architectures.
TPSQLRestore is a utility for restoring a PostgreSQL database from an archive created by TPSQLDump or pg_dump native utility in one of the non-plain-text formats. It will issue the commands necessary to reconstruct the database to the state it was in at the time it was saved. The archive files also allow TPSQLRestore to be selective about what is restored, or even to reorder the items prior to being restored. The archive files are designed to be portable across architectures.
TPSQLTools component allows to run PosgtreSQL diagnostic and repair operations such as Analyze, Cluster, Vacuum and Reindex.
TBDE2PSQLDAC class is intended for the conversion of BDE Database Objects into PostgresDAC Database Objects.
TPSQLStoredProc encapsulates a dataset with a result set that is based on an server stored procedure.
Use TPSQLStoredProc to access PostgreSQL stored procedure in a database. A stored procedure is a grouped set of statements, stored as part of a database server's metadata (just like tables, indexes, and domains), that performs a frequently-repeated, database-related task on the server and passes results to the client.
TPSQLNotify provides the interface to PostgreSQL Asynchronous Notification functionalities. To learn how does PostgreSQL Asynchronous Notification work, please see Asynchronous Notification section of PostgreSQL documentation.
Use TPSQLNotify to organize notifications between client applications about their actions through Postgres database server.
TPSQLCopy is a component for moving data between PostgreSQL tables and standard file-system files. Allows to work with both client and server file systems.
TPSQLCopy may copy data from a file to a table (appending the data to whatever is in the table already), and contents of a table (or even result of a SELECT statement) to a file.
TPSQLDirectQuery is component for high-speed (2-3 times faster then with TPSQLQuery component) data fetching. But it is not TDataset compatible.

PostgresDAC 3.12 is available

This maintenance release updates client, dump and restore libraries and introduces support for PostgreSQL 14.1 functionality

PostgresDAC 3.11 meets RAD Studio 11 Alexandria and PostgreSQL 14!

This release introduces support for RAD Studio 11 Alexandria and PostgreSQL 14 major versions

PostgresDAC 3.10 is available

This maintenance release updates client, dump and restore libraries and introduces support for PostgreSQL 13.3 functionality

PostgresDAC 3.9 meets PostgreSQL 13!

This release introduces support for the new PostgreSQL 13 major version

PostgresDAC 3.8 meets RAD Studio 10.4 Sydney!

This release includes RAD Studio 10.4 Sydney and PostgreSQL 12 support

More news ›


Site map | Search | Privacy Policy | Terms of Use | Contact Us
Copyright © 2000—2024 Microolap Technologies LTD. All Rights Reserved.
All trademarks are the sole property of their respective owners.