Kay Röpke <[email protected]> writes: > the problem really comes down to: > if any part of the app needs access to certain data, certain people > will have access to the data (because there must be some way to access > the username/password combination) otherwise it's useless. > "certain people" depends on the size of the organization, i guess. in > my experience it means either a) devs or b) DBAs. or both for small > companies. outside of those two groups, people don't generally have > access to the systems (accounting, marketing or other "business" > folks).
Agree. To me, this and similar issues like roles, foreign keys, stored procedures, etc. etc. comes down to one thing: Do I want to develop my system in the framework of some RDBMS or in a real programming language like Perl, Java, or whatever the current fashion happens to be. To me the choice is clear. I have never seen anything from a database/RDBMS that I consider even remotely on the level I would expect of a good programming language. I _have_ seen disasters like tens of thousands of lines of Oracle stored procedures implementing business logic etc. It always ends up with one half of the app being implemented in the database, and the other in the application language, which generally is terrible. So this is what I like, and what I think MySQL (and Drizzle) is targeting, which is probably why I like MySQL. So by all means let us have features like foreign keys, stored procedures, row filters etc. They are occasionally useful. Just do not expect me to use then as a general replacement for a real application development framework. But to each his own. - Kristian. _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
