Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

10
  • Good point about the date, this seems like the easiest solution so far. But will there be no problem if I add fields later on? Commented Jun 8, 2017 at 13:07
  • I see, but what if there are lots of different fields to search for? Isn't it bad practice to have a lot of columns? Commented Jun 8, 2017 at 13:26
  • @Soundwave Edited my answer to suggest a way to handle change Commented Jun 8, 2017 at 13:26
  • Edited my post again. What makes your solution (solution 4) more preferable over solution 3 (solution 2 with dates). Because I've read that a lot of columns is not preferable. And there might be a lot of search options. Commented Jun 8, 2017 at 13:30
  • @Soundwave Check the documentation specific to your DBMS but I would be surprised that it is a limiting factor. From my experience, it's very common to have 100+ columns in a table. If you prefer facts, prototype and benchmarck to make sure this is sustainable with a large amount of data and columns Commented Jun 8, 2017 at 13:36