Skip to content

Commit c7f0177

Browse files
committed
README cleanup
Former-commit-id: 225a413
1 parent c3d24e3 commit c7f0177

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

README.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,16 +8,18 @@ pgdiff is written to be easy to expand and improve the accuracy of the diff.
88

99

1010
### download
11-
[osx](https://github.com/joncrlsn/pgdiff/raw/master/bin-osx/pgdiff "OSX version")   [linux](https://github.com/joncrlsn/pgdiff/raw/master/bin-linux/pgdiff "Linux version")   [windows](https://github.com/joncrlsn/pgdiff/raw/master/bin-win/pgdiff.exe "Windows version")
11+
[osx](https://github.com/joncrlsn/pgdiff/raw/master/bin-osx/pgdiff "OSX version")   [linux](https://github.com/joncrlsn/pgdiff/raw/master/bin-linux/pgdiff "Linux version")   [windows](https://github.com/joncrlsn/pgdiff/raw/master/bin-win/pgdiff.exe "Windows version")
1212

1313

1414
### usage
1515
pgdiff [options] <schemaType>
1616

17-
(where options are defined below and &lt;schemaType&gt; can be: ROLE, SEQUENCE, TABLE, COLUMN, INDEX, FUNCTION, VIEW, FOREIGN\_KEY, OWNER, GRANT\_RELATIONSHIP, GRANT\_ATTRIBUTE, TRIGGER)
17+
(where options and &lt;schemaType&gt; are listed below)
1818

1919
I've found that there is an ideal order for running the different schema types. This order should minimize the problems you encounter. For example, you'll always want to add new tables before you add new columns. This is the order that has worked for me, however "your mileage may vary".
2020

21+
Schema type ordering:
22+
2123
1. FUNCTION
2224
1. ROLE
2325
1. SEQUENCE

0 commit comments

Comments
 (0)