host:port/database

RoleName = public,schema1,schema2

Allows setting the port to connect to. D7+ only.

Can instead be specified as a member of the Database paramater.

select typname from pg_type; -- unquoted version
select "typname" from "pg_type"; -- quoted version

Please note that quoted objects names are case sensitive for PostgreSQL. The query above written like this would fail:

db =# select "typname" from "Pg_type";
ERROR: Relation "Pg_type" does not exist
                

The pgExpress Driver should automatically detect your locale settings and use the appropriate decimal separator. However, if you want to force some specific value, this options is available. Set it to the char you want to be the decimal separator (usually either "." or ",").

However, since the "," is the options separator, you'll need to escape that char, like this:

ServerDecimalSeparator = \,

Another exemple:

ServerDecimalSeparator = .

See also ServerDecimalSeparator.

If True, the pgExpress Driver will use Fetch Cursors to retrieve the records from the server. The standard RowsetSize param (check your Kylix/ Delphi documentation) will determine the number of rows retrieved on each operation.

It is required to use this parameter to read the records in blocks since the pgExpress Driver will have to use a totally different method to retrieve the records from the server. Please refer to the section for more details.

If True, the pgExpress Driver will return qualified names on metadata retrieving, such as public.MyTable, pg_catalog.abstime, etc.

This option will only work PostgreSQL 7.3 which supports schemas.

If True, the pgExpress Driver will return the OID field in the list of fields for a table (ISQLConnection.getColumns()).

See also this FAQ entry on OIDs usage with pgExpress.

Controls the Retaining Cursors behavior.

If True, the pgExpress Driver will retain the cursor for the previous SELECT statement and return it if a previous dataset record is acessed again, instead of running the whole query again (dbExpress behavior). No matter how many times the same query is run again, always the same result set is returned (from the internal cache).

If True, the pgExpress Driver will log (into TSQLMonitor) the DECLARE/FETCH commands executed internally as it requests rows from the server. The reason for this special param is that those commands could fill the logs with information not necessary to everybody; you can filter them setting it to False.

An example of unfiltered output (LogDeclareFetch=False):

Starting transaction for DECLARE/FETCH
Starting transaction
>> BEGIN;
>> DECLARE pgeCursor CURSOR for select * from pg_type;
>> FETCH 50 FROM pgeCursor
>> FETCH 50 FROM pgeCursor
>> FETCH 50 FROM pgeCursor
>> FETCH 50 FROM pgeCursor
>> FETCH 50 FROM pgeCursor
Closing cursor pgeCursor
>> CLOSE pgeCursor
Ending DECLARE/FETCH transaction
Rolling back transaction
>> ROLLBACK;

The same operation, but filtered (LogDeclareFetch=True):

>> BEGIN;
Rolling back transaction
>> ROLLBACK;

For more info on DECLARE/FETCH cursors, check Section 6.2, “Fetch Cursors”.