Re: transaction speed and size with Spatial index

What happens is the catalog table record is being constantly updated with latitude and longitude values ( i.e. the Spatial index ). As the update is occurring to the catalog table, the connection pool starts creating 100 to 200 users and trying to update the same record in the catalog table. This is the way the app works because the app is constantly trying to track the position. This record in the catalog table tracks lat/long position. So,

So by design all your sessions wait for one
So whenever you commit, then a next waiting session will immediately update the same record to a new value?


I don't know about your business requirements, but you could

Tanel.

--
http://www.freelists.org/webpage/oracle-l


Other related posts: