Does TUniQuery support simultaneous Requests

Discussion of open issues, suggestions and bugs regarding UniDAC (Universal Data Access Components) for Delphi, C++Builder, Lazarus (and FPC)
Post Reply
randydom
Posts: 3
Joined: Tue 04 Mar 2014 03:06

Does TUniQuery support simultaneous Requests

Post by randydom » Tue 04 Mar 2014 03:11

i want to ask this question ( as it's so important at least for me ) :

I use a TUniQuery component in my project with a PostgreSQL Database , so let's suppose this : there are 10 users trying to Register or Logging at the same time , will the TUniQuery handle all these 10 simultaneous ( Register or logging ) Requests at the same time ? or what will happen please .

I read about using the Pooling Property , will this property be useful so that the my Query can handle simultaneous Requests or should i consider adding other option .

PS : i'm not using a thread to handle my requests i only use a DataModule and i create a TUniQuery on runtime for each Request .

many thanks

AlexP
Devart Team
Posts: 5530
Joined: Tue 10 Aug 2010 11:35

Re: Does TUniQuery support simultaneous Requests

Post by AlexP » Tue 04 Mar 2014 10:06

Hello,

To implement such behavior, you should create a separate thread in your server for each new user. In this case, all actions will be performed in separate threads.

randydom
Posts: 3
Joined: Tue 04 Mar 2014 03:06

Re: Does TUniQuery support simultaneous Requests

Post by randydom » Tue 04 Mar 2014 11:01

AlexP wrote:Hello,

To implement such behavior, you should create a separate thread in your server for each new user. In this case, all actions will be performed in separate threads.
Hello AlexP , that means without using a Thread it will be impossible that the TUniQuery can handle SIMULTANEOUS REQUESTS , although i set the Pooling Property to true ?

many thanks again

AlexP
Devart Team
Posts: 5530
Joined: Tue 10 Aug 2010 11:35

Re: Does TUniQuery support simultaneous Requests

Post by AlexP » Wed 05 Mar 2014 11:41

Pooling allows to save changes in the pool for further their usage and resource saving. For simultaneous query execution, you should implement separate threads for all the connections.

Post Reply