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

Your last comment about the ActiveRecord pattern is what is puzzling me. My exposure to ORMs is only via Rails/ActiveRecord and I can't imagine WHY I would want to write all the boilerplate that it takes care of. And what exactly is so bad about that pattern? Sure, it can't handle all the edge cases that raw SQL can, but one can always drop down to raw SQL when required. We do that for running reports all the time.

Saurabh Nanda
– Saurabh Nanda

2016-08-04 17:08:33 +00:00
Commented Aug 4, 2016 at 17:08
The main reason for not using an ORM is so that you can optimize your queries for specific situations. Implementing the Active Record pattern without an ORM is quite easy: you just add save and find methods to your class, and you can then have different find methods that load different related classes via joins, for example.

Jules
– Jules

2016-08-05 08:52:14 +00:00
Commented Aug 5, 2016 at 8:52

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 »