I should add, though, that the tables I really think this would benefit most are those which don't have interfaces already. I know that good arguments can be made for making User and Entry tidier by fitting them into some sensible scheme, but as for whether it's worth the work, I don't know. My feeling is generally, no, but then I also don't feel qualified to judge that.
However, I do think is that having a generic class for those tables where no interface exists would be time saving and efficient and would prevent duplicating code and therefore worth it. This is really where I feel the argument justifying it lies, and what I was asking whether it would be useful to write.
no subject
However, I do think is that having a generic class for those tables where no interface exists would be time saving and efficient and would prevent duplicating code and therefore worth it. This is really where I feel the argument justifying it lies, and what I was asking whether it would be useful to write.