This content has been marked as final. Show 4 replies
JDeveloper 184.108.40.206 (application deployed on customer's site in Weblogic Server 10.3.6)
Have you upgraded the application to JDeveloper 220.127.116.11 before deploying it to WLS 10.3.6? Note that the requirement is that JDeveloper versions and WLS versions must match
Regarding the problem, its hard to say for us what the problem is as there seems to be custom code involved that we don't know about. One difference could be that your customer site has more data to query than during building the application. It doesn't matter if only the first 100 rows are queried if the SQL itself filters a million data to determine the first 100
I've found the reason for not populating table in popup.
Although there is a limitation to the number of rows displayed in table in the form of additional where clause: "rownum <=n" this part of where clause is added to the VO in overridden method: executeQueryForCollection.
Before executing this method framework is executing: getEstimatedRowCount which when executed for the first time through method getQueryHitCount executes a query against the database (select count(1) from... without my rowum <=n which is added to the query afterwards in above mentioned method executeQueryForCollection).
My question is: if I don't want to add rownum <= n at design-time, where it would be the best place to add it to the query so to avoid above described situation and to have that rownum <= n in place for the count query as well?