tag:blogger.com,1999:blog-8884584404576003487.post5861409810504941605..comments2024-02-29T09:43:12.251-05:00Comments on ORACLENERD: ORA-08177 - IIoraclenerdhttp://www.blogger.com/profile/12412013306950057961noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-8884584404576003487.post-51527195620530198012009-03-01T23:23:00.000-05:002009-03-01T23:23:00.000-05:00I blew my FIRST! opportunity. Damn it.I blew my FIRST! opportunity. Damn it.Clever Idea Widgetryhttps://www.blogger.com/profile/11224068405843575576noreply@blogger.comtag:blogger.com,1999:blog-8884584404576003487.post-73380010738608856582009-03-01T23:16:00.000-05:002009-03-01T23:16:00.000-05:00You are quick!Not sure if it's evident, but I'm fa...You are quick!<BR/><BR/>Not sure if it's evident, but I'm fairly tired of the discussion. Perhaps I'm just not ready for the in-depth conversation the debate entails.<BR/><BR/>However, my gut instinct tells me that, READ COMMITTED being the natural isolation level, READ COMMITTED is what we should use. At least for the time being. <BR/><BR/>I also believe that there is a fundamental flaw in the design in that it's trying to do too much in this single logical transaction. Some of the code is encapsulated in packaged procedure calls, but the trigger stuff is, well, it's crazy.oraclenerdhttps://www.blogger.com/profile/12412013306950057961noreply@blogger.comtag:blogger.com,1999:blog-8884584404576003487.post-35959067546684103082009-03-01T23:05:00.000-05:002009-03-01T23:05:00.000-05:00Dependency on serializable transactions that invol...Dependency on serializable transactions that involves an application of more than a handful of concurrent users is most definitely a a design <B>error</B>. You might as well use flat files to store your data...Clever Idea Widgetryhttps://www.blogger.com/profile/11224068405843575576noreply@blogger.com