Re: Interesting Bugs in 12cR1
From: Rich Jesse <rjoralist2_at_society.servebeer.com>
Date: Thu, 11 Jul 2013 11:44:22 -0500 (CDT)
Message-ID: <54c23c294a68be64600ddf237b754041.squirrel_at_society.servebeer.com>
Hemant writes:
Date: Thu, 11 Jul 2013 11:44:22 -0500 (CDT)
Message-ID: <54c23c294a68be64600ddf237b754041.squirrel_at_society.servebeer.com>
Hemant writes:
> Some bugs that I found interesting :
> http://hemantoracledba.blogspot.com/2013/07/interesting-bugs-in-12cr1.html
Bug 16047938 gets me because it's a new feature that's broken. If it was a regression, I could see how that might be missed -- the product is huge -- but shouldn't QA be verifying that a NEW feature actually works?
Like anything, I'm sure there's more to the story that we'll never know, but it seems embarrassing.
Bug 13877504 -- eww. The better answer to me would be to just turn off threading. Or change every cronjob that logs in via external authentication.
Like I've said before: I'll wait for a few point releases before even trying -- it seems pointless to do so before the ironing is done.
Rich
-- http://www.freelists.org/webpage/oracle-lReceived on Thu Jul 11 2013 - 18:44:22 CEST