Today we features a mini-Q&A with Alex Roedling, MySQL's Senior Product Manager, about all things MySQL, the competition, technology, licensing and more.
Permalink for comment
To read all comments associated with this story, please click here.
That's like saying that it's OK if your filesystem were to randomly truncate files or mix two files together. Becuase, hey, it works and it's fast and who cares if you lose a few bits here and there?
It's interesting that you make an economic argument about using MySQL. I've always maintained that it's far more economical to use a better-designed DBMS. PostgreSQL, FireBird, Oracle, etc, will all let you put your business rules and integrity checking in one centralized place - the database itself. If you do that, you don't have to code your business logic and integrity checks into every app (which saves a lot of time and effort, esp when debugging them). I've worked on projects which use PHP, Perl, Python and Java to talk to the same database. Why write, test and debug your integrity checks in four different languages when you can do it once?
That's like saying that it's OK if your filesystem were to randomly truncate files or mix two files together. Becuase, hey, it works and it's fast and who cares if you lose a few bits here and there?
It's interesting that you make an economic argument about using MySQL. I've always maintained that it's far more economical to use a better-designed DBMS. PostgreSQL, FireBird, Oracle, etc, will all let you put your business rules and integrity checking in one centralized place - the database itself. If you do that, you don't have to code your business logic and integrity checks into every app (which saves a lot of time and effort, esp when debugging them). I've worked on projects which use PHP, Perl, Python and Java to talk to the same database. Why write, test and debug your integrity checks in four different languages when you can do it once?