What are the benifits of PgDac?

Leslie · Post by **Leslie** » Wed 28 Oct 2009 14:21

Hi,

I am looking at AnyDac or possibly UniDac because of their multi back end support, but it appears that their PostgreSQL support may be limited compared to PgDac. Is there a comparison somewhere on the web underlining the advantages PgDac has over these products?

I am also looking for a list of currently unsupported PostgreSQL functionality of PgDac.

With Regards,
Leslie

Plash · Post by **Plash** » Thu 29 Oct 2009 09:55

UniDAC supports most of the PgDAC features.

Usupported features are the following:
- special field types for DATE, TIMESTAMP, and TIME values. UniDAC always uses standard TDateField, TDateTimeField, and TTimeField.
- special field types for geometric and composite types. UniDAC fetches these types as string.
- TPgAlerter component. But we plan to add the TUniAlerter component in one of the next UniDAC builds.
- TPgDump. TUniDump can dump only data.

Leslie · Post by **Leslie** » Fri 30 Oct 2009 09:31

Plash,

Thanks for the info.

Can you answer the other part of my question too? (Unsupported PostgreSQL features of PgDac).

Leslie

Plash · Post by **Plash** » Mon 02 Nov 2009 10:42

PgDAC supports reading and writing all PostgreSQL data types. It supports all other base features (like stored procedures, etc.) and many advanced features (like TPgAlerter, TPgLoader, TPgDump components).

So PgDAC supports all PostgreSQL functionallity that can be used in data access components.

One known problem is the following: PgDAC does not read a new value of a serial column after inserting record unless you set the DMLRefresh property to True. We are planning to solve this problem in one of the future versions.