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.

1

Both ideas will probably lead the OP directly into hell, at least when he picks one and tries to solve all his problems with that ;-)

Doc Brown
– Doc Brown

2017-12-14 19:58:18 +00:00
Commented Dec 14, 2017 at 19:58
@DocBrown Could you please elaborate on your concerns?

Ralf Kleberhoff
– Ralf Kleberhoff

2017-12-15 09:39:44 +00:00
Commented Dec 15, 2017 at 9:39
Most of it you find in my answer. Individual tables (with duplicated attributes) have a high risk to cause maintenance problems. Putting all potential attributes in one monster table is seldom a good approach, too - if you think for a moment of one tenant who wants all available attributes in his application, you would probably not put them in one monster table either. Instead, you would model them according to normalization rules in different child and link tables. And such a split model is still useful even one when each tenants sees only a subset of the whole model.

Doc Brown
– Doc Brown

2017-12-15 14:11:00 +00:00
Commented Dec 15, 2017 at 14:11
... so both of your suggestions heavily violate normalization rules, just in different ways. And I don't think a recommendation for just one single solution, without individual considerations on a per-attribute basis, will serve the OP well.

Doc Brown
– Doc Brown

2017-12-15 14:13:19 +00:00
Commented Dec 15, 2017 at 14:13

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 »