Data Truncation for Attributes without Explicit Length

Problem: You observe data truncation, or device performance and memory issues.

Explanation: When using STRING and BINARY datatypes without explicit length, Unwired WorkSpace internally uses 300 for STRING, and 32768 for BINARY. These values cause runtime truncation if the EIS backend data requires larger size. These values may also cause unnecessary large page size during Object API code generation, and might cause device performance and memory issues

Solution: Double-check all MBO attributes and operation parameters with STRING and BINARY datatypes that do not have explicit length specified, and ensure setting a proper length based on your EIS backend knowledge to avoid data truncation.

Related concepts
AutoCommit Option in JDBC Attributes or Operations
Related tasks
Unwired WorkSpace Crashes When Previewing or Test Executing Large Amounts of Data
Cannot Start Unwired WorkSpace After Upgrade
Cannot Access sampledb
Cannot Access Sample Database After Switching Network Types
Data Source Connection Fails After Installing to a New Directory
Related reference
MS SQL Server 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
Input Parameters Fail to Generate for Complex Data Sources
Client Device Database Performance Issues after Primary Key Changed to Composite