Implement COPY FROM/TO functionality for PostgreSQL (PgDAC component).
PostgreSQL COPY manual:
PostgreSQL 9.2 has a new feature that allows results sets to be returned row by row instead of the whole result set at once.
This is a huge improvement for larger result sets.
See here for more info:
Postgres Advanced Server (PAS) is an extended version of PostgreSQL, it supports Stored Procedures, Packages and Aliasses. Currently, PgDAC does not support executing several of the commands available in PAS.6 votes
The possibility to read/write Geometry-Data-Types of PostGIS (MultiPolygon, Collections etc.) as it is possible with PostGreSQL-Geometry-Data-Types like lseg, polygon etc.6 votes
UniDAC currently only supports OpenSSL 1.0.2. This version won't be supported past 2019-Dec-31.
To avoid problems UniDAC should support OpenSSL 1.14 votes
Actually (v6.2.4), the PgDac TPgDump component does not generate appropriate code for inherited tables, making it useless when inherited tables are used, and we need to get the SQL script to generate the given schema.
TPgDump should support tables inheritance and:
- create base tables before inherited tables
- use the inherits clause within the table creation sql statement
- do not generate insert statements for base tables data, only for inherited tables
The RefreshQuick method (https://www.devart.com/mydac/docs/devart.mydac.tcustommydataset.refreshquick(system.boolean).htm) seems very useful to refresh only the new records from big datasets. Ideally, make it possible to specify the name of the TIMESTAMP field so we don't have to create a duplicate - mine are called "created" for example). Maybe we don't even need the TimeStamp field for Postgresql ?1 vote
- Don't see your idea?