Edit - Software Engineering Stack Exchange

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.

How do you decide if the approach is (still) reasonable? The devil on my shoulder says I only need that one table "object" containing every possible field.

Marco Borchert
– Marco Borchert

2016-11-08 15:32:24 +00:00
Commented Nov 8, 2016 at 15:32
do you agree with the first blog entry you linked on it’s necessary to make (too) many (too) costly joins (right at the bottom) referencing the kind of solution @Vlad described in his answer? From my (limited) understanding that is exactly what an RDBMS is used for: specifying relations; There is not even a need for additional indices since all joins use primary keys only.

Marco Borchert
– Marco Borchert

2016-11-08 15:46:09 +00:00
Commented Nov 8, 2016 at 15:46

Add a comment |

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)

<https://example.com>

[example](https://example.com)

<a href="https://example.com">example</a>

formatting help »
answering help »