Just to emphasize the parent's point about singular vs plural, there are a lot of reasons to go with singular: * Singular is much friendlier to find/replace, d

Just to emphasize the parent's point about singular vs plural, there are a lot of reasons to go with singular: * Singular is much friendlier to find/replace, due to the inconsistency of pluralization. * A good practice is to name association tables by concatenation of the tables being associated (when the association doesn't correspond to a previously named entity). teacher_class is a much better name than teachers_classes, and definitely avoid teacher_classes. * As you move up the stack, structs, interfaces and classes have strong singular conventions. If you spend much time at higher levels, the habits you develop can lead to little bugs when working deeper in the stack.