support of Delphi 2006 (Win32 edition), 5-7, C++Builder 5-6;
full compatibility with all the existing data-aware controls and report designers;
full support of the BLOB fields;
TDBImageEx component for JPEG images support included in the package for free (with sources);
detailed help system and a lot of various demo applications;
and much more...
TEDBDataBase provides discrete control over a connection to a single database in a database application.
Use TEDBDataBase when a database application requires any of the following control over a database connection:
Persistent database connections;
Customized database server logins;
TEDBTable encapsulates a database table.
Use TEDBTable to access data in a single database table. TEDBTable provides direct access to every record and field in an underlying database table. TEDBTable 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 TEDBTable by right-clicking on the TEDBTable and using the pop-up menu.
TEDBQuery encapsulates a dataset with a result set that is based on an SQL statement.
Use TEDBQuery to access one or more EnterpriseDB tables in a database using SQL statements. TEDBQuery 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.
TEDBUpdateSQL applies cached updates on behalf of queries or stored procedures that can't post updates directly.
Use a TEDBUpdateSQL object to provide SQL statements used to update read-only datasets represented by TEDBQuery 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 EnterpriseDB returned a read-only result set. This usually happens for queries made against multiple tables. Such queries are, by SQL-92 definitions, read-only.
TEDBBatchExecute component can execute SQL scripts containing more than one SQL statement.
TEDBMacroQuery is the decessor of TEDBQuery component and supports all of its properties, methods, events, and functionalities.
TEDBMonitor monitors dynamic SQL passed to the EnterpriseDB server.
TEDBDump is a component for backing up a EnterpriseDB database. It makes consistent backups even if the database is being used concurrently. TEDBDump 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 TEDBBatchExecute, 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 TEDBRestore 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.
TEDBRestore is a utility for restoring an EnterpriseDB database from an archive created by TEDBDump 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 TEDBRestore 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.
TEDBTools component allows to run EnterpriseDB diagnostic and repair operations such as Analyze, Cluster, Vacuum and Reindex.
TBDE2DBEDAC class is intended for the conversion of BDE Database Objects into EDBDAC Database Objects.