Skip to main content
Ask A Question
You’re not receiving notifications from this thread.

PG conflict changing the name of an attribute in the database

General • Asked by Damian Nelwep

Hi everyone,

I'm having an issue after changing the name in a "Relationship" Controller and Model (the name is "follow / unfollow" and before was "meaw / unmeaw" (which I endend founding pretty bad and got back to something more classic). I also changed it in the database and many other places, but PostGres displays an error message as follow :

PG::UndefinedColumn: ERROR:  column relationships.meawed_id does not exist
LINE 1: ...users"."id" = "relationships"."follower_id" WHERE "relations...
: SELECT  1 AS one FROM "users" INNER JOIN "relationships" ON "users"."id" = "relationships"."follower_id" WHERE "relationships"."meawed_id" = $1 LIMIT $2

I wonder if I have to take care of this with another migration or directly using PG interface... The problem is that I don't remember the password or how to authenticate. I thought it might be better to reset the database.

Thank you so much in advance for your advice

Login or Create An Account to join the conversation.

Subscribe to the newsletter

Join 31,152+ developers who get early access to new screencasts, articles, guides, updates, and more.

    By clicking this button, you agree to the GoRails Terms of Service and Privacy Policy.

    More of a social being? We're also on Twitter and YouTube.