|
PostgresDAC - License Program - Educatief
Direct access components for PostgreSQL and
Pervasive Postgres Powerful component suite for Delphi/C++Builder and
PostgreSQL 7.x, 8.x/Pervasive Postgres. It allows you to
create Delphi/C++Builder applications with direct access to PostgreSQL/Pervasive
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 » Lees meer...
|  |
Alle prijzen zijn in Euro incl. BTW en excl. verzendkosten.
E-mail of bel 023 548 20 19 voor licenties, upgrades en andere vragen.
Direct access components for PostgreSQL and
Pervasive Postgres Powerful component suite for Delphi/C++Builder and
PostgreSQL 7.x, 8.x/Pervasive Postgres. It allows you to
create Delphi/C++Builder applications with direct access to PostgreSQL/Pervasive
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);
- 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;
- TNT Unicode Controls Wrappers package
for Unicode applications for free (with sources);
- detailed
help system and a lot of various demo
applications;
- and much more.
What's new in version
2.5.1 - Ability to specify library name and path
for PostgresDAC added
- CID, XID, TID types are
mapped to TIntegerField from now
- Parameters support added
to TPSQLDirectQuery
- TPSQLCopy.RowsAffected property added
- TPSQLDatabase.IsSSLUsed function added
- TPSQLDump.Encoding property added
- TPSQLDump: gzip compression option for
plain output format added
- TSQLDataset/TADODataset to TPSQLQuery conversion
added for TBDE2PSQL component
- Database property of components
assigned automatically on creation
- v8.3.7 client libraries added
- 8.3.7 dump & restore libraries (pg_dump.dll, pg_restore.dll) added
- "Access Violation error may occur if long SQL
used (>1Mb)" bug fixed
- "Error on start IDE
if libpq.dll library can not be loaded" bug
fixed
- "Misordering of TPSQLDump output for composite types"
bug fixed
- "Property UpdateObject does not exist" bug
in TDBE2PSQL component fixed
- "Stream read error for
BLOBs may occur if non UTF8 encoding used"
error fixed
- "TPSQLCopy silently processed errors" bug fixed
- "TPSQLDatabase.Comment is always blank" bug fixed
- "TPSQLDataset.Locate failed
for UUID type" bug fixed
- "TPSQLUpdateSQL may incorrectly
use BIT VARYING type in parameters" bug fixed
- "UUID, TIME WITH TIME ZONE, TIMESTAMP WITH TIME
ZONE field types may be displayed garbled" bug
fixed
- "Ðŝutput not re-assigned back to screen after
dump is done" bug fixed
- Small memory leak
in TPSQLDirectQuery eliminated
- "AV occurs inside TPSQLDirectQuery.Open method
if associated database is closed" bug fixed
- "Invalid
UTF-8 byte sequence detected" for IDE versions odler
than 2009 bug fixed
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 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. -
Meer vergelijkbare producten, klik hier
|