PostgresDAC description
BDE replacement for Borland Delphi/C++Builder

PostgresDAC is PostgreSQL BDE replacement for Delphi/C++Builder.

PostgresDAC allows to create Delphi/C++Builder applications with the direct access to PostgreSQL DB without BDE and ODBC.

PostgresDAC is a tool that allows you create applications.

This components set was developed for easy migration of existing projects from BDE/ODBC scheme to the native one.

Interface is BDE-like and TDataSet compatible.

TDBImageEx component for JPEG images in BLOBs support included in package for free (with sources).

Here are some key features of "PostgresDAC":

· 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 cached 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 when cached updates are enabled. 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.


Limitations:

· fully-functional time-limited trial