Slashdot Mirror
'Most Important Ever' MySQL Reaches Beta
An anonymous reader writes "The open source database company says it is 'fixing 10 years of critcism in one release', and is aiming at boosting enterprise take-up." Stored procedures. Triggers. Views. It's like it'll be a real DB!
Wake me up when they fix this. Oh, and are they finally adding an "enterprise feature" called "subselect"?
___
If you think big enough, you'll never have to do it.
yes, well, those of us who *really* know what we're doing are the ones writing the applications (in LISP, undoubtedly), and we consider your DBA job as a commodity-level position that would be nonexistent without our applications there to ensure the dumb-ass user can even get to your inherently worthless data. and we write libraries to ensure "referential integrity". you can write your logic in the application and fuck it up, you can write your logic in the DB and fuck it up, and yes, you can butter your bread on either side and still fuck it up. do any of these pointless debates really matter? no. computing is increasing exponentially. there are no godamn golden bullets! what works is what works...
thats why jobs are going to india. it's a godamn commodity cause no matter what you're going to hire a billion programmers anyway just to the maintain the application and to tell the users what the application is even doing and to clean up the data after some dumb-ass user entered in the wrong data, referential integrity or not, and to get the charts lined up properly for management and to....
First off, you seem angry about something. Did you spend a lot of money on a DB cert, only to be angered that others are getting the same job done with OSS and good programming techniques?
I already mentioned my apps don't focused on accounting.
I was under the impression that transactions enable you to lump together a series of queries into one transaction, so if something fails, none of the queries/inserts execute. If I'm wrong, then I stand corrected.
Lastly, I have experience with high traffic websites as well as small business apps. I am not new to application design and certainly don't just 'hack' something together. Just because I don't use commerical products doesn't mean I can't design and implement professional solutions.
I understand the importance of data integrity but also keep in mind that in the 8 years that my career has focused on this business, I never once had a query or insert fail. Never once did I have data corruption. Of course I've encountered bugs in the applcation layer that caused bad db inserts; but nothing was unfixable.
You can try to sell me tornado insurance all day long, but that doesn't mean I'm required to purchase it.
So what if the accounting system is off by $12,000,000? It's fast.
Who cares if the customers actually get the products they ordered? It's fast.
Who cares if we bill our customers for the right amount? It's fast.
Yhere's a lot of FUD on mySQL. Someone please help me. Show me a few example how mySQL's lack of transaction has result into some real business organization's accounting system going off by $12,000,000! Hay! It's being used by millions for about a decade for now and should have made gazallions of transactions! Surely there should be a LOT of real life examples doom's day example by now!
What? You find none? Do you need any more prefect example on what a FUD is?