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.
-
2I really hope you oversized a problem of creating a new field in RDBMS table to make the statement more dramatic. The database table needs to be very special (or the new field type needs to be something exceptional) to really create a problem to add one field.Alexey Zimarev– Alexey Zimarev2016-02-26 13:18:19 +00:00Commented Feb 26, 2016 at 13:18
-
Yes, but it's never just one field ...theMayer– theMayer2016-02-26 13:44:28 +00:00Commented Feb 26, 2016 at 13:44
-
1I would say more often it is just one field. Dramatic schema changes aren't that often. I am not a fan of using RDBMSes with OO design due to impedance mismatch. However, adding new types (tables) and properties (columns) are relatively easy in both worlds although in NoSQL it is indeed a bit easier. But complex changes are pain in both cases. Even worse it becomes in event-sourced system with snapshots, in opposite how pleasurable the development experience for such system is.Alexey Zimarev– Alexey Zimarev2016-02-26 14:12:15 +00:00Commented Feb 26, 2016 at 14:12
-
I see that relational databases are often used as the "universal hammer" to solve data storage needs - when in fact there are very specific reasons to use them. In a carefully-contemplated system, one rarely has to worry about the issues I wrote about in my answer - I'm addressing at a more general audience who may not have have the experience to arrive at an appropriate system design up-front.theMayer– theMayer2016-02-29 17:12:57 +00:00Commented Feb 29, 2016 at 17:12
-
There is no discrepancy between relational model and it does usually map to real world just as well as any other kind of model. Some operations will be easier with one kind and other with other kind. The trouble is when you create a model of one kind (object-oriented) and try to implement it with tools of another kind (relational). That does not work well. But real world is not object-oriented. It just is and you model it. And have to use the right tools for the selected kind of model.Jan Hudec– Jan Hudec2016-10-04 19:13:55 +00:00Commented Oct 4, 2016 at 19:13
Add a comment
|
How to Edit
- 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
How to Format
-
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>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. design-patterns), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you