10 ms·

MySQL's default storage engine has been InnoDB -- a high-quality OLTP storage engine which is fully ACID compliant -- for thirteen years now. Meanwhile MySQL's

MySQL's default storage engine has been InnoDB -- a high-quality OLTP storage engine which is fully ACID compliant -- for thirteen years now. Meanwhile MySQL's default settings have included strict sql_mode (giving a hard error on data type mismatches, overflows, etc) for eight years. These have been available as non-default options for 20+ years, and larger MySQL users have long enabled them before they were defaults. Yes, the defaults certainly should have changed earlier, especially re: strict sql_mode, I won't dispute that. However on the default storage engine side, the historical reasoning makes perfect sense: InnoDB and MySQL were owned by different companies. Oracle purchased the makers of InnoDB in 2005 and didn't purchase Sun (incl MySQL) until 2010. Once both products were owned by Oracle, they made InnoDB the default storage engine in the next major MySQL release that same year. In any case, your claims of "decades of misleading marketing" about transactions is completely fictional. This simply did not happen for "decades" and has not been a discussion point of any sort for a very, very long time. Serious MySQL shops were never using MyISAM at scale in the first place.

justinclift 3y ago
[flagged]
- evanelias 3y ago
  > Yeah, good luck with that. That's a completely nonsensical reply to the contents of my comment. I'm not the same person you were originally responding to up-thread.
  - justinclift 3y ago
    [flagged]
    - samlambert 3y ago
      [flagged]
      - justinclift 3y ago
        Alternatively, I don't have the energy to deal with people pushing misinformation. :/
        evanelias 3y ago
        You chose to come into a thread about MariaDB, you wrote some verifiably factually incorrect statements about MySQL, and then you complain about not having the energy to discuss further? I took time out of my Sunday to write a fact-based rebuttal to your false claims in this thread. The dates in my comment are all verifiable on Wikipedia, among other places. And yet your response is childish repetition, followed by a citationless comment claiming that my own comment was misinformation. Since you're a Golang enthusiast (as am I), perhaps I can reframe this in a more relatable way. Imagine that it's the year 2035, and there's an HN thread about Golang. Some Go-hater chimes in that no one should ever trust Go because of decades of misleading marketing ("no one needs generics!"), GOPATH being stupid, and lack of a module dependency system. What would your response to this be in 2035, knowing full well that these issues were far in the past and that the claim of "decades" is at best an extreme exaggeration?
        justinclift 3y ago
        > you wrote some verifiably factually incorrect statements about MySQL That's the kind of bullshit I'm meaning. I have no energy left to deal with trolls, and that means you.
        evanelias 3y ago
        MySQL was first released in 1995. A decade is 10 years. Plural decades means 20 or more years. You claimed MySQL made decades of misleading marketing about transactions. That would mean they were making such statements in 2015 or later. That is verifiably factually incorrect, considering that InnoDB (a fully ACID-compliant storage engine) was made the default storage engine in 2010, and prominent MySQL users had already switched to InnoDB en masse from 2005 to 2008, some even earlier. The previous storage engine (MyISAM) was garbage that wasn't even crash-safe, so at scale its deficiency was plainly obvious. I am not posting "bullshit" or "trolling". Your statement was incorrect and this is simple date math.

justinclift 3y ago

[flagged]

evanelias 3y ago
> Yeah, good luck with that. That's a completely nonsensical reply to the contents of my comment. I'm not the same person you were originally responding to up-thread.
- justinclift 3y ago
  [flagged]
  - samlambert 3y ago
    [flagged]
    - justinclift 3y ago
      Alternatively, I don't have the energy to deal with people pushing misinformation. :/
      - evanelias 3y ago
        You chose to come into a thread about MariaDB, you wrote some verifiably factually incorrect statements about MySQL, and then you complain about not having the energy to discuss further? I took time out of my Sunday to write a fact-based rebuttal to your false claims in this thread. The dates in my comment are all verifiable on Wikipedia, among other places. And yet your response is childish repetition, followed by a citationless comment claiming that my own comment was misinformation. Since you're a Golang enthusiast (as am I), perhaps I can reframe this in a more relatable way. Imagine that it's the year 2035, and there's an HN thread about Golang. Some Go-hater chimes in that no one should ever trust Go because of decades of misleading marketing ("no one needs generics!"), GOPATH being stupid, and lack of a module dependency system. What would your response to this be in 2035, knowing full well that these issues were far in the past and that the claim of "decades" is at best an extreme exaggeration?
        justinclift 3y ago
        > you wrote some verifiably factually incorrect statements about MySQL That's the kind of bullshit I'm meaning. I have no energy left to deal with trolls, and that means you.
        evanelias 3y ago
        MySQL was first released in 1995. A decade is 10 years. Plural decades means 20 or more years. You claimed MySQL made decades of misleading marketing about transactions. That would mean they were making such statements in 2015 or later. That is verifiably factually incorrect, considering that InnoDB (a fully ACID-compliant storage engine) was made the default storage engine in 2010, and prominent MySQL users had already switched to InnoDB en masse from 2005 to 2008, some even earlier. The previous storage engine (MyISAM) was garbage that wasn't even crash-safe, so at scale its deficiency was plainly obvious. I am not posting "bullshit" or "trolling". Your statement was incorrect and this is simple date math.