Hi Luis: Thanks for the rapid response. I'll work on your MySQL fix... in the meantime, what further details can I provide regarding the sqlite3 adapter issue?
--Dean Luis Lavena wrote in post #960735: > On Thu, Nov 11, 2010 at 9:49 AM, Dean Richardson <li...@ruby-forum.com> > wrote: >> presence of the sqlite3-ruby gem and other associated dependencies. The >> overflow, etc., but none of the fixes I've found so far there seem to >> help. >> >> Any suggestions for how to make either test database approach (sqlite3 >> or mysql) work would be greatly appreciated. >> > > Hello, > > To better understand what is going on with sqlite3 adapter will > require more details. > > As for the mysql error, in your database.yml, just copy your > configuration from development section and rename the database to your > test one. > > Ensure the socket line is not there, as is the one affecting your > mysql execution. > > HTH, > -- > Luis Lavena > AREA 17 > - > Perfection in design is achieved not when there is nothing more to add, > but rather when there is nothing more to take away. > Antoine de Saint-Exupry -- Posted via http://www.ruby-forum.com/. _______________________________________________ rspec-users mailing list rspec-users@rubyforge.org http://rubyforge.org/mailman/listinfo/rspec-users
