Known Issues for Sybase Unwired WorkSpace – Mobile Business Object Development

Workaround: Change the attribute name for one of the MBOs so that the attributes are not identical.

For one-to-one and one-to-many relationships, all primary keys in the parent MBO must map to a child MBO. Unwired WorkSpace enforces this restriction by, in some cases, silently modifying the MBO primary key definition.

For example, a parent MBO has two primary keys (primeOne and primeTwo), and a relationship is created based only on the PrimeOne primary key. In this case, Unwired WorkSpace automatically unchecks primary key for primeTwo in order to follow the relationship rule.

This can result in unintended consequences because of modified run-time behavior.

Workaround: You must create another relationship for any additional primary keys.

Cached data is marked as logically deleted when certain activities occur in the client application or back end.

Workaround: If logically deleted MBO rows must be purged from the cache by the System Administrator, define a separate cache group for the MBO in Unwired WorkSpace. This allows the administrator to purge the data manually in Sybase Control Center. For details, see System Administration of the Unwired Platform > System Administration > Package Administration > Data Management Overview > Cache Data Management > Cache Refreshes > Purging a Cache Group.

YYYY-MM-DD HH:MM:SS.SSS WARN    MMS          Thread-466
[com.sybase.sup.server.SUPDomain] On Non primary servers, you could not
execute createDsyncDataZip()
java.lang.Exception: On Non primary servers, you could not execute
createDsyncDataZip()
        at com.sybase.sup.server.cluster.ClusterUtils.createDsyncDataZip
(ClusterUtils.java:816)
        at com.sybase.sup.server.SUPDomain.incrementDomainVersion
(SUPDomain.java:779)
        at com.sybase.sup.admin.server.DomainAdminImpl.deployJar
(DomainAdminImpl.java:291)

Workaround: An administrator can identify which server is the new primary server using Sybase Control Center and relaying the specific connection properties to you. Set up a new connection profile using those properties, then redeploy using that new connection. See Sybase Unwired WorkSpace - Mobile Business Object Development > Configure > Configure - Eclipse Development Environment > Creating a Sybase Unwired Server Connection Profile for how to create a new Sybase Unwired Server connection profile.

Workaround: Always use the Eclipse deployment wizard to create a new datasource server endpoint, rather than using the Administrator console to manually create one.

Workaround: Sybase recommends you map all fields of a structured argument to parameters.

Workaround: Define a primary key before you deploy.

This scenario can cause Unwired WorkSpace to stop responding.

Workaround: Exit and restart Unwired WorkSpace with the same workspace. The renamed project appears in Unwired Navigator.

Workaround: Do not use these words as part of the MBO name.

UPDATE sampledb.dba.department 
SET 
dept_name=:dept_name, 
dept_head_id=:dept_head_id 
WHERE (dept_id = :dept_id) 
AND (dept_name = :old.dept_name 
OR (dept_name IS NULL AND :old.dept_name IS NULL)) 
AND (dept_head_id = :old.dept_head_id 
OR (dept_head_id IS NULL AND :old.dept_head_id IS NULL))

Caused by: com.sybase.vader.da.jdbc.MinCheckAffected
  RowCountException 
at com.sybase.vader.da.jdbc.JdbcCheckAffectedRowCount.execute
  (JdbcCheckAffectedRowCount.java:27) 
at com.sybase.vader.service.interaction.PipelineComposite
  InteractionOperation.execute(PipelineCompositeInteraction
  Operation.java:54) 
at com.sybase.vader.cache.modify.CacheInvalidating
  Operation.execute(CacheInvalidatingOperation.java:29) 
at com.sybase.vader.mms.DataServiceImpl.execute
  (DataServiceImpl.java:197)

Workaround:Remove the old value portions (of string column comparisons) from the where clause.

Because Unwired WorkSpace cannot retrieve the datatype of the parameter in the where clause when you access Visual SQL, the datatype is set to String by default, which can lead to a type conversion error.

Workaround: Ignore the warning message. The MBO is created successfully.

The seven affected datatypes are: long varbit, varbit, uniqueidentifier, xml, long nvarchar, nchar, and nvarchar.

Workaround: None.

Workaround: Use a result-set filter to limit the digits for time to show only hh:mm:ss without the milliseconds. Refer to Result set filter documentation for the steps involved.

If a package name contains uppercase character, as in "Test," and this package uses a role-related feature, the role feature does not work on device as expected.

Workaround: Do not use uppercase letters in the package name.

When you edit an MBO definition, you see a question, similar to Data source or definition has changed. Do you want to refresh and remap? If you select yes, you see an error message similar to The metadata is not in sync with the backend data source. This error is caused by a limitation with the JDBC driver.

When the enterprise information system (EIS) is an SQL Anywhere database and you create a relationship between two string attributes that map from a char field, and the nullability setting for the char field in the parent table is not null, the char field in child table is nullable. The relationship will not work.

Workaround: Manually update the query statement for the parent MBO to apply the rtrim() function to the char field in the column list.

select region from sampledb.dbo.sales_regions

select rtrim(region) as region from sampledb.dbo.sales_regions

Workaround: Update the stored procedures that jConnect™ for JDBC™ uses for accessing database metadata by running the SQL script provided with EBF #16903 for jConnect, available from the Sybase EBFs Maintenance page at http://downloads.sybase.com (login required). You can use the dbisql utility provided with SQL Anywhere version 10 to run the sql_asa10.sql file contained within the EBF to update these JDBC-access stored procedures.

Workaround: Save Unwired WorkSpace projects after generating code or deploying to Unwired Server.