4 ms·

Hmm. I see "ENGINE=MyISAM" in the code. Nowadays I can't stomach using MyISAM for anything I care about not having some sort of corruption. Given sufficient

by jzawodn 15y ago

Hmm. I see "ENGINE=MyISAM" in the code. Nowadays I can't stomach using MyISAM for anything I care about not having some sort of corruption. Given sufficient time and scale, I've seen far too many issues with MyISAM. It'd be great to be able to specify that in the code so the user can opt for InnoDB (or engine of their choice). Perhaps a pull request is in my future...

ginzasparrow 15y ago
You could've cloned the repo and started hacking on it in the time it took you to write that.
- jzawodn 15y ago
  Agreed. https://github.com/cosimo/TicketServer/pulls https://github.com/cosimo/TicketServer/pulls
  - ginzasparrow 15y ago
    Damn you for undermining my snarky comment. Cheers.
    - cosimo 15y ago
      Merged too.
cosimo 15y ago
I seem to remember that the MySQL behavior this is based on will only work with the MyISAM engine. In fact, Flickr is using MyISAM for this, IIRC. Anyway, your changes make perfect sense, so I merged them. Will try what happens to the test suite with InnoDB.
- cosimo 15y ago
  Actually it works just fine ;)