When you select a table mapping row in the Table Mappings pane, information about the table appear in the Details pane. The Details pane has the following tabs:
The Column Mappings tab shows the mapped columns.
You can mark a column mapping for deletion by selecting a row in the Column Mappings tab and choosing Edit » Delete. The column mapping is deleted when you save the model. Deleting a column mapping means the column will not be created in the remote database when the model is deployed.
The Column Mappings tab shows the following information for the selected table mapping:
Remote column name The name of the column in the remote database table.
R# (Remote column number) This column indicates the order in which columns are returned by a SELECT * FROM tablename command.
Remote column data type The data type.
Mapping direction The mapping direction of the column.
A column's mapping direction is dependent upon the mapping direction of the table to which it belongs. A column can either have the same mapping as its table or not be synchronized. For example, if the table has a Bi-Directional table mapping, the table's columns can either be Bi-Directional or Not Synchronized.
If the column mapping direction is Not Synchronized, the column is part of the remote database schema. When the model is deployed, the column is created on the remote, but no information is synchronized to it.
If you don't want the column to be created on the remote, delete it from the model. You can not delete primary key columns. See Modifying how deletes are handled.
Consolidated column name The name of the column in the consolidated database table.
If your remote database existed before you created your synchronization model, the information in this column represents a best guess that you should check.
C# (Consolidated column number) This column indicates the order in which columns are returned by a SELECT * FROM tablename command.
Consolidated column data type The data type.
The Download Type tab shows the following information for the selected table:
Timestamp column name Specify the name of the column to be used for timestamp-based downloads.
Use timestamp columns in consolidated table Select this option to add a timestamp column to each consolidated table if the timestamp column does not already exist.
Use shadow table to hold timestamp column Select this option to create a shadow table for each synchronized consolidated database table. Shadow tables are created with the same owner as the base table.
See Modifying the download type.
The Download Deletes tab applies if the download type is Timestamp. That is, in the Table Mappings pane, the Download Type is set to Timestamp and the Download Deletes column is selected. See Mappings: Table Mappings.
This tab allows you to view and modify the way that the deletions on the consolidated database are recorded for timestamp-based synchronization. The Download Deletes tab shows the following information for the selected table:
Use shadow table to record deletions Select this option if you want to use shadow tables to track deletes in the consolidated database.
Shadow tables are created for each synchronized table in the model. Each shadow table has two columns: one that holds the primary key for the table, and another that holds the timestamp. Shadow tables are created with the same owner as the base table.
Timestamp column name Specifies the name of the Timestamp column. The default Timestamp column name is last_modified.
Use logical deletes Select this option if you want to use logical deletes in the consolidated database to help with download deletes. Logical deletes use a status column to keep track of whether rows are valid. The following options specify how the status column tracks deletes:
Column name Specifies the name of the column that is used to indicate if a row has been deleted. This column is added if it is not already present. The default name is deleted.
Value if row deleted Specifies the value that is generated when a row is deleted. The default is Y.
Value if row not deleted Specifies the value that is generated when a row is not deleted. The default is N.
See:
The Download Subset tab applies if you subset data by user, remote ID, or by a custom subset. The Download Subset tab shows the following information for the selected table:
Use a column in the consolidated table Select this option to use a column in each consolidated table. To use this option, you must have a table on your consolidated database that contains MobiLink user names, or tables that you can join to create MobiLink user names. You choose your MobiLink user names when you deploy, so you can choose names that match existing values on your consolidated database. (The column you use for MobiLink user names must be of a type that can hold the values you are using for the user name.)
Column name Specify a column containing the MobiLink user name or remote ID.
Use a column in a joined relationship table Select this option and identify the MobiLink user name or remote ID with a join. You can specify:
Table to join Specify a column from the consolidated table.
Column to match Specify a column from the chosen table to join.
Join condition Create a join condition by choosing a column from the table chosen in the Table Mappings pane and choosing a column from the table specified in the Table to Join field above.
See Remote IDs, and Introduction to MobiLink users.
Custom If you chose to create a custom subset, the Download Subset tab allows you to specify tables and an expression. Multiple tables must be separated by commas.
Tables to add to the download cursor's FROM clause Type the table names.
SQL Expression to use in the download cursor's WHERE clause Type the SQL expression.
See Writing download_cursor scripts, and Modifying the download subset.
The Conflict Resolution tab applies if you chose to resolve conflicts based on a timestamp.
Timestamp column Enter the timestamp column here.
The Status tab shows any informational, warning, or error messages for the table mapping that is selected in the Table Mappings pane.
| Send feedback about this page via email or DocCommentXchange | Copyright © 2008, iAnywhere Solutions, Inc. - SQL Anywhere 11.0.0 |