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.
I don't think some (or perhaps most) of the gotchas in MySQL will be fixed (at least in near term). It will break many apps that use MySQL.
MySQL has always had these philosophies: *) don't complain too much; *) do/pick the best for user, silently if possible; *) easiness and speed comes first, data integrity second.
Imagine the complaints of people when suddenly, for example, they cannot insert string longer than the defined length (MySQL currently just truncates the long string silently instead of returning an error). Or MySQL rejects a large integer that is larger than the integer column size (currently MySQL just inserts the largest allowed value instead, silently).
MySQL just forgives and allows too much, and many users depend on this behavour.
I don't think some (or perhaps most) of the gotchas in MySQL will be fixed (at least in near term). It will break many apps that use MySQL.
MySQL has always had these philosophies: *) don't complain too much; *) do/pick the best for user, silently if possible; *) easiness and speed comes first, data integrity second.
Imagine the complaints of people when suddenly, for example, they cannot insert string longer than the defined length (MySQL currently just truncates the long string silently instead of returning an error). Or MySQL rejects a large integer that is larger than the integer column size (currently MySQL just inserts the largest allowed value instead, silently).
MySQL just forgives and allows too much, and many users depend on this behavour.