EntitySQLProcessor Transaction time-out

[Rohit Rai-2]

Hi folks,

I encountered a transaction time-out while performing a MySQL query from
EntitySQLProcessor perhaps due to the huge size of the result set.


Is it possible to increase the time-out or is there any other way to deal
with this? Please advice.


Earlier, when I faced the same issue while performing a delete query I
dealt with it by limiting the rows. But, this time I need to perform a
select query.


Rohit Rai
www.hotwaxsystems.com

[Rajesh Mallah]

Hi Rohit ,

for huge-sized resultset you should ideally use paging.

Also try to see how long does the query takes to execute.

you may use count(*) in place of the selected columns
to estimate it.

regds
mallah.

On Mon, Jun 11, 2018 at 4:39 PM, Rohit Rai <[hidden email]>
wrote:

> Hi folks,
>
> I encountered a transaction time-out while performing a MySQL query from
> EntitySQLProcessor perhaps due to the huge size of the result set.
>
>
> Is it possible to increase the time-out or is there any other way to deal
> with this? Please advice.
>
>
> Earlier, when I faced the same issue while performing a delete query I
> dealt with it by limiting the rows. But, this time I need to perform a
> select query.
>
>
> Rohit Rai
> www.hotwaxsystems.com
>

[Rohit Rai-2]

Hi Rajesh,

Thanks for your reply. I tried count(*) beforehand it returned a time-out roll
back.


Rohit Rai
www.hotwaxsystems.com



On Mon, Jun 11, 2018 at 5:13 PM, Rajesh Mallah <[hidden email]>
wrote:

> Hi Rohit ,
>
> for huge-sized resultset you should ideally use paging.
>
> Also try to see how long does the query takes to execute.
>
> you may use count(*) in place of the selected columns
> to estimate it.
>
> regds
> mallah.
>
> On Mon, Jun 11, 2018 at 4:39 PM, Rohit Rai <[hidden email]>
> wrote:
>
> > Hi folks,
> >
> > I encountered a transaction time-out while performing a MySQL query from
> > EntitySQLProcessor perhaps due to the huge size of the result set.
> >
> >
> > Is it possible to increase the time-out or is there any other way to deal
> > with this? Please advice.
> >
> >
> > Earlier, when I faced the same issue while performing a delete query I
> > dealt with it by limiting the rows. But, this time I need to perform a
> > select query.
> >
> >
> > Rohit Rai
> > www.hotwaxsystems.com
> >
>

[Rajesh Mallah]

Hi Rohit ,

Please see if some obvious indexes are being missed.
if using postgresql , 'explain analyze' is your friend. If queries
are not optimal other optimizations are short-term relief.

regds
mallah.

On Wed, Jun 13, 2018 at 11:26 AM, Rohit Rai <[hidden email]>
wrote:

> Hi Rajesh,
>
> Thanks for your reply. I tried count(*) beforehand it returned a time-out
> roll
> back.
>
>
> Rohit Rai
> www.hotwaxsystems.com
>
>
>
> On Mon, Jun 11, 2018 at 5:13 PM, Rajesh Mallah <[hidden email]>
> wrote:
>
> > Hi Rohit ,
> >
> > for huge-sized resultset you should ideally use paging.
> >
> > Also try to see how long does the query takes to execute.
> >
> > you may use count(*) in place of the selected columns
> > to estimate it.
> >
> > regds
> > mallah.
> >
> > On Mon, Jun 11, 2018 at 4:39 PM, Rohit Rai <[hidden email]>
> > wrote:
> >
> > > Hi folks,
> > >
> > > I encountered a transaction time-out while performing a MySQL query
> from
> > > EntitySQLProcessor perhaps due to the huge size of the result set.
> > >
> > >
> > > Is it possible to increase the time-out or is there any other way to
> deal
> > > with this? Please advice.
> > >
> > >
> > > Earlier, when I faced the same issue while performing a delete query I
> > > dealt with it by limiting the rows. But, this time I need to perform a
> > > select query.
> > >
> > >
> > > Rohit Rai
> > > www.hotwaxsystems.com
> > >
> >
>