Question
Verizon
IN
Last activity: 26 Oct 2022 0:53 EDT
Maximum Elapsed time for Obj-Browse & RDB Methods
Report definition rule form have an option of Maximum elapsed time in data access tab, Is there any way we can achieve this in Obj-browse and RDB-* methods.
Looking for Maximum elapsed time option for individual queries of Obj-browse and RDB-* methods.
Note: Alreday explored JDBC level timeout setting but it will apply for all the queries.
***Edited by Moderator Marije to change Type from Discussion to Question***
Ordina
NL
@MuraliM16668102I think the easiest way to currently do this, is by retrieving a report definition through an activity that has a time-out on its query. It could be worthwhile to see if you can leverage this setting for an Obj-Browse aswell, but I doubt how OOTB that is going to be.
With RDB-List you can use (Postgres)SQL's 'LIMIT' keyword aswell but that is basically the MaxRecords implementation of an Obj-Browse. You could look at the 'statement_timeout' variable that controls timeout on the database level as opposed to the JDBC level.
Interesting to hear more solutions to this problem!
Verizon
IN
@BasG0629 Thanks for your response.
Extensively used Obj-browse and RDB-* methods in the application, Converting to Report Definition is major design change.
And also to retrieve the BLOB data, Obj-browse is the only option.
Maximum elapsed time setting available on Report Definition cannot be leveraged for Obj-Browse, OOTB handled specific to Report.
Obj-Browse has Max Records and RDB-List has ROWNUM keyword in oracle, basically these are to limit the number of results, but we cannot specify time limit.
JDBC read timeout (or) Database statement_timeout are Generic, These will apply for all the queries.
Looking for timeout on individual query rather than common setting across.