Updated to be compatible with node-postgres #4
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I started out just fixing two bugs:
username
setting, because it's calledusername
in sequelize's config file, anduser
inpg
postgres
, but since you were removing the database from the configuration object, it would try to connect toprocess.env.USER
instead, which most likely doesn't exist. So now we will either connect toprocess.env.POSTGRES_DB
(as defined by postgres) orpostgres
.Then I got carried away when I saw a bunch of duplication. What I ended up doing:
pg
withpg-promise
so that we don't need a bunch of callbacks all over the placeThis repo looks abandoned, so I'll be using my fork, but I thought I'd offer up the changes in case you were interested.