3 ms·
It's not just gh-ost. pt-osc is much safer to use when you don't have to worry about updating foreign keys. Here are some of Github's reasons for not using the
by sciurus 8y ago
It's not just gh-ost. pt-osc is much safer to use when you don't have to worry about updating foreign keys.
Here are some of Github's reasons for not using them: https://github.com/github/gh-ost/issues/331 https://github.com/github/gh-ost/issues/331
I think this is pretty normal for heavy MySQL users, honestly. When I was at Eventbrite we didn't use them for the same reasons.
- rantanplan 8y agoI've read about their reasons, I just didn't want to open a discussion about it :D Deciding to implement constraints on the application/business layer is something that github can probably do, in the same vein that Facebook can create their own PHP compiler. I just think that you can't use these examples as effective arguments on whether someone should use FKs or not. I guess whatever brute-force solutions these companies would apply, on any given problem, would probably work one way or the other.