Edit - Stack Overflow

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.

Rev

3

Liguibase's best practices recommend keeping schema creation scripts as a set of sequential scripts to be ran in order. While this is a good best practice I don't see how it would works without a central repository, which is un-GIT.
– Frank Schwieterman
Commented Mar 17, 2010 at 2:49
1

Well, it would work across git just fine if you are careful about your id= and author= tags. In theory each user would have their own author entry (GOOD) and if you do something reasonable with id=, say YYYYMMDD_REV, then you are pretty much good to go. Even with git, most everyone has a 'central repo', for a given project. 99% of people don't have somethiing 'central'. Again, Liquibase files are just plan text XML-ish files, with a stack of commands to execute against a given DB (or set of). Chances are 99% of all projects would have 0 issues following this in practice, even with DVCS's.
– zie
Commented Mar 30, 2010 at 4:03
+1 For this answer. This what we use in several projects. Ids need to be unique within one xml file only. If you name the ids from the use case being implement they are unique enough. You have to be careful not modifying already applied changesets otherwise you will get checksum errors.
– bernardn
Commented May 5, 2013 at 10:01

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 »

Collectives™ on Stack Overflow