Skip to content

Commit

Permalink
README cleanup
Browse files Browse the repository at this point in the history
Former-commit-id: 225a413
  • Loading branch information
joncrlsn committed Mar 1, 2016
1 parent c3d24e3 commit c7f0177
Showing 1 changed file with 4 additions and 2 deletions.
6 changes: 4 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,16 +8,18 @@ pgdiff is written to be easy to expand and improve the accuracy of the diff.


### download
[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")
[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")


### usage
pgdiff [options] <schemaType>

(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)
(where options and &lt;schemaType&gt; are listed below)

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".

Schema type ordering:

1. FUNCTION
1. ROLE
1. SEQUENCE
Expand Down

0 comments on commit c7f0177

Please # to comment.