Auf YouTube findest du die angesagtesten Videos und Tracks. Außerdem kannst du eigene Inhalte hochladen und mit Freunden oder gleich der ganzen Welt teilen.
Oracle makes the worst database system ever imagined by anyone ever. Can’t even insert multiple rows in the same statement, you have to put multiple insert statements and Oracle sues you for dreaming about any other database.
Oracle sues for everything, when they sue you, they can ask for their payment to be related to the total employees of the company, to take that as users of the Oracle Database (trademark)(copyright)(shat my pants) or Java (do I need to repeat?). Yeah, they sue for EVERYTHING.
The video glances at this, but this happened where I work, so I can’t give the direct sources for the case against the place I work, but if even the Oracle employees talk about the draconic bullshit Oracle does, imagine what happens to the companies/governments they sue.
I can chime in here with “my former employer hired a full-time lawyer after being sued by Oracle over something trivial”. Company of less than 200. They settled and they still have at least one permanent legal staffer.
Oracle licenses software by CPU (or at least they did). But not in the way you think, they mean by discrete logical CPUs. So if you virtualize one of their apps and give the VM 4 CPUs, do you need four licenses? No, since it could run on any of the CPUs in the host, you need to buy however many that is.
I went to look for more info on this and couldn’t find anything reliable, but I did find an article from Amazon saying that if you run something like this in AWS, you need enough licenses to cover the entire goddamn AWS zone.
This is one of the issues with the tech side of their business. They’ve been around a long time, and certain features that other databases had in the 90s were just put into Oracle a few years back. Devs don’t always have a good handle on the new capabilities, especially when the old code without the feature is done and working.
Oracle makes the worst database system ever imagined by anyone ever. Can’t even insert multiple rows in the same statement, you have to put multiple insert statements and Oracle sues you for dreaming about any other database.
What’s this?
Oracle sues for everything, when they sue you, they can ask for their payment to be related to the total employees of the company, to take that as users of the Oracle Database (trademark)(copyright)(shat my pants) or Java (do I need to repeat?). Yeah, they sue for EVERYTHING.
Can I get an article/source about this? I’m in the mood to be mad about Oracle
The video glances at this, but this happened where I work, so I can’t give the direct sources for the case against the place I work, but if even the Oracle employees talk about the draconic bullshit Oracle does, imagine what happens to the companies/governments they sue.
I can chime in here with “my former employer hired a full-time lawyer after being sued by Oracle over something trivial”. Company of less than 200. They settled and they still have at least one permanent legal staffer.
https://www.tacticallawgroup.com/oracle-software-audit-blog
Fun
Oracle licenses software by CPU (or at least they did). But not in the way you think, they mean by discrete logical CPUs. So if you virtualize one of their apps and give the VM 4 CPUs, do you need four licenses? No, since it could run on any of the CPUs in the host, you need to buy however many that is.
I went to look for more info on this and couldn’t find anything reliable, but I did find an article from Amazon saying that if you run something like this in AWS, you need enough licenses to cover the entire goddamn AWS zone.
Everything that Oracle makes really feels like they got the idea from a random engineer they stuck up on their lunch break.
Yeah, pretty sure you can do multi row insert though
This is one of the issues with the tech side of their business. They’ve been around a long time, and certain features that other databases had in the 90s were just put into Oracle a few years back. Devs don’t always have a good handle on the new capabilities, especially when the old code without the feature is done and working.