Slashdot Mirror
Why Some Devs Can't Wait For NoSQL To Die
theodp writes "Ted Dziuba can't wait for NoSQL to die. Developing your app for Google-sized scale, says Dziuba, is a waste of your time. Not to mention there is no way you will get it right. The sooner your company admits this, the sooner you can get down to some real work. If real businesses like Walmart can track all of their data in SQL databases that scale just fine, Dziuba argues, surely your company can, too."
1) Oracle Power Objects
2) OS/2 support
Both of these cost me hideous amounts of money. I do telecomms billing, and if you think you can do that with MSSQL (which cant handle timestamps properly), then think again. I certainly cant afford to have another clusterfuck involving MSSQL - if a client wants to use it, let him go elsewhere. i don't want him sueing me cos his billing data is worthless. Yes I know someone else will get the business - I have had bills from several telecomms companies who probably do use MS software! If my competition get sued it suits me fine.
Sent from my ASR33 using ASCII
Define irony: A guy who clearly has no experience with large scale database system telling others how bad SQL is while using a tiny fringe asstastic software package as an example.
Your entire first paragraph is based on 100% factually incorrect statements. Perhaps you should investigate the various SQL standards out there before you talk out your ass. I have a large web app that runs on Oracle, PostgreSQL and MSSQL, with the same queries. Slightly different scripts to create the database to deal with the differences in stored proceedures, so theres a little bit of truth there, but I could have moved the stored procedures to a different location if I wanted to.
Your second paragraph is clearly written by ... well, again someone who has never used a high end database. Any high end database worth its salt is designed to deal with raw disk space for its tables. Again, just because you've never had any experience outside of dicking around in your basement in Linux doesn't mean you know what your talking about. And MythTV is possibly one of the biggest piles of shit in existence. It can't even detect when the database server is malfunctioning. Don't bring up some MySQL based app like its a real database app. They aren't, ever. MySQL is used by people who don't have enough experience to realize how much it sucks. And yes, I know Wikipedia uses it. And yes, MySQL is still a fucking retarded way for them to store data.
As for the last two paragraphs ... why bother, you're clearly disconnected and the rest is just you talking out your ass. Perhaps one should consider that its not SQL that sucks since so many people are capable of doing things with it just fine. Perhaps you should look a little closer to home and consider that your inability to use it is what sucks.
Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
Nobody ever got fired for choosing IBM is the way I have always heard it. And used in that context, I agree. My experience with IBM products has been nothing but bad.
I don't know about other Oracle software, it's probably bloatware. But the Oracle DB is an awesome product. Proper handling of views, the ability to perform hierarchical queries, and SQL*Loader are alone worth the (high) cost of admission. Before you dismiss those, try working with hierarchical data in MySQL without nested querying and looping or a non scalable set of union queries. Also, try importing massive amounts of data and see what this does to performance on MySQL. Then try querying a view on some large tables in MySQL and notice the order in which the view's where clause is executed in relation to your query's where clause. For you to have that opinion, I can imagine you've never done these things in MySQL.
Oracle is a very good DB, but is also sensitive to being (im)properly managed. Since it's not a toy like MySQL or MSSQL, you need to hire a real DBA, one who actually understands databases and not some point-and-click monkey to work with MSSQL or someone who knows a few linux commands to work with MySQL (yay mtop and mysqldump!) And your devs need to actually understand how to design and index tables and write queries properly. IOW, basic competence for anyone who claims to know anything about databases.
You don't like Oracle because either a) you have suffered a bad implementation at the hands of incompetent DBAs/bad programmers, or b) are one of the preceding.
I have worked with MSSQL, Oracle, and MySQL extensively. Oracle leaves them all in the dust.
blah blah blah
Have you used SQL Server? I thought not.
yes and it's utter crap.
Truth is like the sun. You can shut it out for a time, but it ain't goin' away. - Elvis Presley (source: imdb.com)