Client Device Database Performance Issues after Primary Key Changed to Composite

Problem: You observe client device database performance issues caused by redundant findByPrimaryKey object queries or index/indices created unnecessarily for the query/queries.

Explanation: If the MBO's single attribute primary key is changed to a composite primary key, Unwired WorkSpace automatically generates redundant object queries for each added primary key attribute with Create Index selected. This behavior causes client device database performance issues.

Solution: Remove the redundant query or queries, and for any object query, check if the index or indices are needed. Remove any unnecessary index or indices.

Related concepts
Troubleshoot Code Generation
Related tasks
Unwired WorkSpace Crashes When Previewing or Test Executing Large Amounts of Data
Cannot Access Sample Database After Switching Network Types
Data Source Connection Fails After Installing to a New Directory
Attribute Length Set Incorrectly for Operation and Load Parameters
Related reference
JDBC Connection Errors
Mobile Business Object Errors
Preview Errors for a Web Service Mobile Business Object
Compiler Errors When Deploying Device Applications
Deploying to Unwired Server Fails
Deploying to Unwired Server in a Cluster Fails
Data Truncation for Attributes without Explicit Length
Input Parameters Fail to Generate for Complex Data Sources