The SpatialWare writer module stores FME features in a SpatialWare database. The SpatialWare writer module provides the following capabilities.
-
Transaction Support: The SpatialWare writer provides transaction support that eases the data loading process. Occasionally, a data load operation terminates prematurely due to data difficulties. The transaction support provides a mechanism for reloading corrected data without data loss or duplication.
Note: WARNING: This functionality is currently available only for SQLServer. Also, in case more than one reader or writer is accessing SpatialWare through FME (which is possible using FME Objects), then concurrency issues may arise. In such a case, we use isolation levels for transactions as READ_COMMITTED. This means that if we have a writer that writes a feature on a table, then, until the time this transaction is committed, any attempt to read the same table by another reader will cause the program to hang. The reason for that is that SQLServer will maintain a lock on the table until the transaction gets committed. Currently, the user cannot set the transaction isolation levels, but this may be changed in the future.
- Table Creation: The SpatialWare writer module uses the information within the FME mapping file to automatically create SpatialWare tables as needed. If a mapping file table definition has a spatial column, then the associated SpatialWare spatial column is also created.
- Table Validation: When data is loaded into an existing table, the SpatialWare writer module performs validation operations between the table definition in the mapping file and that within SpatialWare. All discrepancies found are logged. All critical discrepancies result in the data load operation being halted.
- Non-homogeneous Aggregate Loading: Provides the ability to load non-homogeneous aggregates into SpatialWare tables, as supported by SpatialWare.
- Update Capability: This functionality is provided for SQLServer and not for Informix. The SpatialWare writer module enables features to be updated in SpatialWare through the use of specified keys and the UPDATE mode of operation. If area replacement of features is desired, this can also be accomplished by combining the capabilities of the SpatialWare writer with the SpatialWareQueryFactory. Refer to Modes of Operation (for SQLServer only) for more detail on how to use this keyword.
- Delete Capability: This functionality is provided for SQLServer and not for Informix. Refer to Modes of Operation (for SQLServer only) for more detail on how to use this keyword.