This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I have not got opportunity yet to work on spatial databases but I am curious to learn about them. Does this book contains details about how data storage in spatial database differs from normal database.
What happens to special datatypes like LOB,BLOB,CLOB etc..
How indexes are maintained in spatial databases.
SCJP SCWCD AIX SOA
The significant problems we face cannot be solved by the same level of thinking that created them -- Albert Einstein
In terms of data types, PostGIS (or Oracle Spatial) simply adds some extra data types to your PostgreSQL (or Oracle) RDBMS. All the regular data types are still there.
Spatial data tends to come with a lot of scalar (non-spatial) attributes e.g. a table listing hospitals might include the location (spatial data) but also the name, street address, phone number, size etc. So if you include a spatial data column on a particular table, it becomes a spatial data table and you can apply various spatial functions to the spatial elements of the data e.g. find the nearest hospital to your current location.
If there are no spatial data columns, then it's just a regular table. In both cases, you can still do all the usual SQL stuff on the non-spatial elements in the data. And of course you can combine spatial and non-spatial operations e.g. find the nearest hospital with a name that contains "X" (no idea why you would do this, of course!), which is one of the many benefits of using a spatial database.