change pg gem to pg_sequel gem#127
Open
jpynn wants to merge 1 commit into
Open
Conversation
|
heroku db:push will soon be replaced with pg:push, which won't use taps, so wouldn't have this problem. It'll have all of its own, new problems! If you want a preview check out heroku/heroku-pg-extras#42 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 was running into an issue connecting using taps with postgresql. (uninitialized constant Sequel::Postgres::PGError).There seems to be a namespace collision of some kind when using the PG gem
Some other people who had the issue
http://stackoverflow.com/questions/4589305/heroku-dbpush-error-uninitialized-constant-sequelpostgrespgerror/4595970#4595970
A description of my own problem
http://stackoverflow.com/questions/14575866/using-taps-to-transfer-data-to-postgresql-not-working