Thread

Oracle on the hook to pay data centre investors even if site has no electricity

158 points · 154 comments · Betelbuddy

gchamonlive · 1790335420 · focus · HN ↗
A too-big-to-fail about to fail certain it'll be bailed out? Another comment* raised a question about investments in fuel cells that could have been just for show. Are they doing max damage to leech as much cash as possible before implosion or it's just... I mean, it's oracle it's a mystery to me how they make so much money with selling crapware, so it might just be business as usual?
*<a href="https://news.ycombinator.com/item?id=49842884">https://news.ycombinator.com/item?id=49842884
1. philipallstar · 1790336197 · focus · HN ↗
  I don't love Oracle, but they made so much money selling the best relational database on the planet for 40 years.
  1. jiggawatts · 1790337165 · focus · HN ↗
    "The best", but you'll be sued if you publish benchmarks: <a href="https://en.wikipedia.org/wiki/David_DeWitt#DeWitt_Clause" rel="nofollow">https://en.wikipedia.org/wiki/David_DeWitt#DeWitt_Clause
    Every time I use Oracle, I regret it.
    Just this month, I tried to hook it up to a modern .NET app with the latest Oracle client and discovered that if you cancel a transaction, the connection enters a broken state and is returned to the connection pool, "infecting it". After a half a dozen of those, the whole app server just dies with endless cancellation related exceptions. This isn't even the only such bug, apparently there's a whole family of pool-corruption bugs that have workaround config settings and everything!
    This was with version 23.26.301 which suggests that they've had a lot of major releases, bug fixes, etc... but basic functionality like "connect successfully to the database server every time" is totally broken and has been for many years.
    The issue tracker forums have tumbleweeds rolling through them and play the sound of wolves howling in the distance to provide just the right kind of "what are you still doing here?" ambiance.
    marcosdumay · 1790343270 · focus · HN ↗
    My favorite bug of the .Net connector is how the entire API supports async operations, but the underlying implementation can't tell two different executions of the same query apart, so it's random whether each call will get their own results or some other ones.
    But polluting the poll with unusable connections is just Oracle copying the MS-SQL's thing. The C# recommended coding practices will automatically deal with this. (Not that you would want to follow them, but you may want to look and copy this part.)
    jiggawatts · 1790386344 · focus · HN ↗
    > the underlying implementation can't tell two different executions of the same query apart
    Got a reference for that?

Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.