After adding another migrate, rake db:migrate simply gives me the
following error:
PGError: ERROR: relation “sessions” already exists
seems the self_down method does not do its job…
thank you for any suggestions.
After adding another migrate, rake db:migrate simply gives me the
following error:
PGError: ERROR: relation “sessions” already exists
seems the self_down method does not do its job…
thank you for any suggestions.
This is most likely an error in your migrations. Can you gist/pastie
the ones in question and send the link?
On Sun, Mar 14, 2010 at 11:41 AM, John U. [email protected]
wrote:
To unsubscribe from this list, please visit:
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
Kyle W. wrote:
This is most likely an error in your migrations. Can you gist/pastie
the ones in question and send the link?On Sun, Mar 14, 2010 at 11:41 AM, John U. [email protected]
wrote:
To unsubscribe from this list, please visit:
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
thank you for the reply. By trying to attach the migrate to post to
you, I realized that there are two files created for session with same
code - that is why? the reason I did not realize that is because the old
system use 01_…rb as naming convention, the new system use time stamps
as prefix.
Thank you!!!
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.
Sponsor our Newsletter | Privacy Policy | Terms of Service | Remote Ruby Jobs