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

Logging changes independently of applications

Some spatial applications require that the old and new values in the schema be tracked so that the changes can be traced back in case of errors. For example, new surveying measurements from the field can be used to update the geometries for the existing land parcels, but the older values need to be tracked for a certain amount of time in the database in case of disputes. Oracle database provides an auditing technology called database auditing that can be used to monitor and track all database level actions. This auditing can be done for individual actions such as DML SQL statements or DDL SQL statements, or any other database level action. Database auditing is typically done to account for actions taken at the schema, table, or an other object level to monitor actions of specific users for accounting purposes, investigate suspicious activity, monitor and gather statistics for specific database operations, and for compliance purposes. Therefore...