Well the problem is I am working on rdf query engine for persistent RDF
data. The data is stored/structured in a specific way in the database.
When i perform updates in parallel, because there are cross table
dependencies, I end up with inconsistencies, For example One transaction
reads to see if there is a resource so as to add a property where it is
a subject. Then an other transaction deletes the resource after the
first has decided that the resource is there but before it added the
property.
Thus it would be helpful for me to avoid the difficult task of
dependency based locking and just lock the whole database.
any ideas?
Rodrigo De León wrote:
On 9/14/07, Panagiotis Pediaditis <pped@xxxxxxxxxxxx> wrote:
... there is a specific case where i need it.
Don't really know, but, explain what the case is, and maybe someone
could help you.
---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend
