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.

Required fields*

Rev

That's what I would be looking for - something independent of the database. Contrast with an in-situ version control that is not immune to a faulty piece of code corrupting the whole database including the version history.

therobyouknow
– therobyouknow

2011-02-01 19:27:14 +00:00
Commented Feb 1, 2011 at 19:27
+1 This approach gives fine granularity but still the same safety of controlling the whole database stage outside of the database itself. Safety because the database itself isnt used to version control itself - it could get corrupted, rather this is done externally. Fine granularity because each change can be recognised rather than a complete snapshot containing everything. Also because this is a working solution - it must be some feet to get the "undo" side of a change working.

therobyouknow
– therobyouknow

2011-02-01 19:33:14 +00:00
Commented Feb 1, 2011 at 19:33

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 »