Book Image

Applying and Extending Oracle Spatial

By : Siva Ravada, Simon Greener
Book Image

Applying and Extending Oracle Spatial

By: Siva Ravada, Simon Greener

Overview of this book

Spatial applications should be developed in the same way that users develop other database applications: by starting with an integrated data model in which the SDO_GEOMETRY objects are just another attribute describing entities and by using as many of the database features as possible for managing the data. If a task can be done using a database feature like replication, then it should be done using the standard replication technology instead of inventing a new procedure for replicating spatial data. Sometimes solving a business problem using a PL/SQL function can be more powerful, accessible, and easier to use than trying to use external software. Because Oracle Spatial's offerings are standards compliant, this book shows you how Oracle Spatial technology can be used to build cross-vendor database solutions. Applying and Extending Oracle Spatial shows you the clever things that can be done not just with Oracle Spatial on its own, but in combination with other database technologies. This is a great resource book that will convince you to purchase other Oracle technology books on non-spatial specialist technologies because you will finally see that "spatial is not special: it is a small, fun, and clever part of a much larger whole".
Table of Contents (20 chapters)
Applying and Extending Oracle Spatial
About the Authors
About the Reviewers
Table Comparing Simple Feature Access/SQL and SQL/MM–Spatial

Workspace Manager

Spatial applications often have the need to work with multiple versions of the data, for example, a city planning application might provide design choices for adding new sub-divisions to the city. At the same time, a reviewer should be able to look at all the possible designs and choose the best design. This requires access to multiple versions of the data. Some of the common reasons for multiversioning of data are concurrency (multiple users working on different designs), history, and what-if scenario creation. The concurrency here is different from the concurrency provided by the database. Another requirement is to keep the changes available beyond the lifetime of the database transaction, especially for what-if scenarios, for example, with the database transaction model, one application user cannot make changes and make them visible to some other users without committing the changes so that they are visible to all the users on the database. This concept is called a long...