Forum OpenACS Development: These problems are PostgreSQL only, or Oracle too?

Collapse
22: These problems are PostgreSQL only, or Oracle too? (response to 1)
Posted by Andrew Piskorski on 07/18/06 07:18 PM
Are the deadlock and duplicate revision_id problems discussed in this thread 100% specific to PostgreSQL? And OpenACS on Oracle is not subject to these problems at all? It sounds as if that's the case, but I haven't yet heard anyone say so for sure...
Collapse
23: Re: These problems are PostgreSQL only, or Oracle too? (response to 22)
Posted by Dave Bauer on 07/18/06 07:32 PM
Oracle does not use cr_dummy, so it should not be subject to duplicate key issues.
Collapse
24: Re: These problems are PostgreSQL only, or Oracle too? (response to 22)
Posted by Gustaf Neumann on 07/18/06 10:56 PM
Oracle has triggers on views, so it uses per default a stored procedure, id does not need the trick with cr_dummy in the generated postgres rule; oracle cannot have this issue with duplicates. The proposed version is closer to the oracle version.

I am not sure, how Oracle deals with updates on foreign keys, but i would expect, it does not have this problem as well. It is likely, that in times before MVCC, postgres did not have these issues either.

Both problems are postgres related. Oracle might have problems on its own, but not these. So far, with this patch, i have not seem both of the problems any more.