Just as an aside, if you are just experimenting with small things, SQLite works really REALLY well. I recommend maybe giving it a shot ... as long as you don't go all crazy outside of Rails' handling of SQL, then the portability of your code from SQLite to almost any other DB adapter (my experience has been with PostgreSQL) is relatively easy.
On Mar 5, 7:24 pm, jsulmar <[email protected]> wrote: > Thanks for the responses. > > After reading and experimenting a lot today, I have solved, or at > least worked around, the problems for my installation. > > It seems: > 1. rails 2.2.2 requires a connection to a working database even if the > application does not use a database (e.g. "Hello World"). Otherwise, > you get the "SayController#hello" message > > 2. the default database used by rails 2.2.2 is sqlite3, so if you want > to use mysql you need to create the project with "rails my_app -d > mysql" ( or you can edit database.yml) > > 3. the mysql gem installer must be told where MySQL has been > installed. > "sudo gem install mysql -- --with-mysql-dir=/usr/local/mysql" > > 4. after successfully installing the mysql gem, my "Hello World" > application still produced a browser message "dlsym(0x1ee0dc0, > Init_mysql): symbol not found ". The mysql gem does not seem to work > with 64-bit MySQL. By installing the 32 bit MySQL package I was able > to resolve this final issue. > > Whew! I'm lucky it only took 2 days. Now I can start creating some > real bugs. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
