Two things that come to mind:
1. Did the migration creating the posts in the db run through correctly?
2. Did you start your "rails server" (be it script/server, passenger or whatever) in development mode?
Two things that come to mind:
1. Did the migration creating the posts in the db run through correctly?
2. Did you start your "rails server" (be it script/server, passenger or
whatever) in development mode?
Felix
In response to 1. The migration ran fine. I thought I'd repaired a
similar error when I previously tried to run the migration by changing
the client library in /bin. Could this be the problem?
In response to 2. I initiated the server with ruby script/server
command. I would presume it's running in development mode as the
application is reloaded on page refresh.
I've already installed the MySQL gem so that's not the issue. localhost
or the address I specified are both fine to use as the host. I even went
as far back as to ensure a database existed (despite my migration
running without a problem).
To solve the issue, I replaced the client library and restarted my
server.