Announcing: Slashdot Deals - Explore geek apps, games, gadgets and more. (what is this?)

Thank you!

We are sorry to see you leave - Beta is different and we value the time you took to try it out. Before you decide to go, please take a look at some value-adds for Beta and learn more about it. Thank you for reading Slashdot, and for making the site better!



Slimmed Down MySQL Offshoot Drizzle is Built For the Web

rasilon Re:Oh man. (370 comments)

He seems to have a tendency to represent the worst possible uses of various things as typical usage, and ignore a number of useful things.

For example, he claims that the security uses of stored procedures have been replaced by role based access control. That's incorrect. If you want to audit changes to a table using RBAC then the user not only needs access to the audit table but must always update it themselves. A user could easily cover up changes by simply omitting the audit row, or adding false data. The use of triggers and stored procedures can enforce the audit, and protect it from malicious update.

His claim that triggers are a bad idea because a novice DBA once disabled them on a production database, not realising that they existed, is just silly. The fix is to ensure that people get a clue before they get superuser access! Triggers are a standard part of every big modern database, and a standard part of any training program.

I could go on, but I don't really fancy debunking every silly thing people write about databases...

more than 6 years ago


rasilon hasn't submitted any stories.


rasilon has no journal entries.

Slashdot Login

Need an Account?

Forgot your password?