diff --git a/README.md b/README.md index ec412d0..3c77455 100644 --- a/README.md +++ b/README.md @@ -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] - (where options are defined below and <schemaType> can be: ROLE, SEQUENCE, TABLE, COLUMN, INDEX, FUNCTION, VIEW, FOREIGN\_KEY, OWNER, GRANT\_RELATIONSHIP, GRANT\_ATTRIBUTE, TRIGGER) +(where options and <schemaType> 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