TUniTable, PostgreSQL and FetchAll option

Discussion of open issues, suggestions and bugs regarding UniDAC (Universal Data Access Components) for Delphi, C++Builder, Lazarus (and FPC)
Post Reply
cross_join
Posts: 13
Joined: Wed 11 Feb 2015 17:34

TUniTable, PostgreSQL and FetchAll option

Post by cross_join » Thu 29 Oct 2015 10:48

Hello all,
When setting

Code: Select all

UniTable.SpecificOptions.Values['FetchAll'] := 'false';
UniDAC open a second connection.

What are the reasons to use second connection?
What PostgreSQL particularities do this impact?

azyk
Devart Team
Posts: 1119
Joined: Fri 11 Apr 2014 11:47
Location: Alpha Centauri A

Re: TUniTable, PostgreSQL and FetchAll option

Post by azyk » Fri 30 Oct 2015 11:03

PostgreSQL doesn't support simultaneous usage of several transactions within the context of one session. So, before calling the TUniQuery.Open method, PgDAC will use a separate connection instance for fetching data to a dataset with FetchAll = False.

However, if the TUniConnection.StartTransaction method was called before opening such dataset, then PgDAC won't use a separate connection instance for data fetching.

cross_join
Posts: 13
Joined: Wed 11 Feb 2015 17:34

Re: TUniTable, PostgreSQL and FetchAll option

Post by cross_join » Fri 30 Oct 2015 12:22

azyk, thank you for explanations.

azyk
Devart Team
Posts: 1119
Joined: Fri 11 Apr 2014 11:47
Location: Alpha Centauri A

Re: TUniTable, PostgreSQL and FetchAll option

Post by azyk » Fri 30 Oct 2015 13:15

If any other questions come up, please contact us.

Post Reply