

Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Guidance on best practices for using the guidewire query api, including recommendations for creating property references, improving the performance of queries using contains(), addressing dot notation performance issues, and choosing the appropriate query type (entity query, row query, etc.) based on the specific requirements of the application. Key concepts such as the use of the groot, qroot, vbroot, and aroot query types, as well as the importance of checking for the existence of entities and avoiding certain query methods like hasmatch(), countwhere(), and select().count. The information presented in this document can be valuable for developers working with the guidewire platform, as it provides practical guidance on optimizing the performance and efficiency of their database queries.
Typology: Exams
1 / 2
This page cannot be seen from the preview
Don't miss anything!


Guidewire Query API Test 2023-
Property Reference - ANSWER When writing queries create a property reference only to persistent fields in the database For example: EntityType#Property Best practice for using contains() - ANSWER add an initial predicate that uses an index Benefits: This enables the database to filter out most of the rows and then execute the contains on a sub-set Which entity column attribute must typically be set to true when compareIgnoreCase() is used? - ANSWER supportsLinguisticSearch What can you do to improve the performance of a query that uses contains()? - ANSWER Add an initial predicate that uses an index Addressing dot notation performance issues - ANSWER use ArrayLodaer class for example myArrayParent.arrays("MyArrayChildReference") Checking for existence of an entity - ANSWER Just check for the existence of an entity if the number of results are not important , verify the results of a targeted query are not empty What methods for queries should be avoided for checking entities? - ANSWER 1. Avoid hasMatch()
aRoot - ANSWER array load query that retrieves IDs of array members
Row query - ANSWER use a single database query on the main entity and the related entities to provide to provide subset of properties you need
Choosing which query type to use - ANSWER use and entity query unless performance is not adequate
use row queries when you want to apply a database aggregate function to a column
What table alias name is used for a row query in the context info? - ANSWER qRoot
When would you use a row query instead of an entity query? - ANSWER 1. When the performance of an entity query is inadequate
Where does clicking the "Show Queries" button take you? - ANSWER The aggregated queries view