Book Image

Applying and Extending Oracle Spatial

Book Image

Applying and Extending Oracle Spatial

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
Credits
About the Authors
About the Reviewers
www.PacktPub.com
Preface
Table Comparing Simple Feature Access/SQL and SQL/MM–Spatial
Index

Packaging summary


Which method of packaging our functions is the best?

  • Standalone functions: These are great for developing and testing algorithms or creating something one off or standalone that can be given to others. But they could become unwieldy, if they grow too many interdependencies.

  • Packages: These allow for shared package variables, which are related to some logical function, but are more loosely coupled in relation to each other or to the data stored in the package.

  • Types: These allow for the consistent and homogeneous packaging of all the methods of an object with its persistent data. Methods in an object type tend to be tightly coupled with the object data as they provide the property inspectors and manipulators for them.

Programming with object types is clean and logical. While within Oracle it is possible to store any object type in a database table (persisting it across database sessions), storage of the T_GEOMETRY type is not recommended for the simple reason that it is presented...