Wednesday, April 4, 2012

JDev/ADF sample - Bad Practice Use Case for LOV Performance Implementation in ADF BC

  • Bad Practice Use Case for LOV Performance Implementation in ADF BC. If you want to learn something well, there is nothing better as to learn bad practices first. Really, by knowing bad practices - you will start to follow best practices just automatically, because there will be simply no bad practices left. If serious, I would like to post one use case that was discovered recently during my work - terribly slow LOV performance in ADF BC. After debugging session, it was discovered - when selecting LOV value, LOV SQL statement was executed around 20 - 25 times. With such SQL statement duplication, of course we can not expect great performance for LOV's, especially with complex SQL cases. Because of specific requirements, there were no EO Associations created to get LOV description, LOV was created based on transient attribute directly. However, this is not a problem, problem is elsewhere.
    Download - LOVByNameGroovy.zip

No comments: