Comments on: Generating a Rails project configured to use MySQL

By: cakebaker

cakebaker — Wed, 25 Mar 2009 14:58:21 +0000

@rbn: You are welcome!

By: rbn

rbn — Mon, 23 Mar 2009 17:01:41 +0000

fantastic… :)) thank you very much for your kind and quick response!

By: cakebaker

cakebaker — Mon, 23 Mar 2009 16:03:41 +0000

@rbn: You can define the variable RAILS_DEFAULT_DATABASE and set it to mysql, see the hint I added to the article.

Hope that helps!

By: rbn

rbn — Sun, 22 Mar 2009 18:56:21 +0000

Hi!
just wandering…
does anybody know how do you config rails to make mysql and not sqlite the default adapter?
thnx

By: cakebaker

cakebaker — Sun, 15 Mar 2009 16:39:25 +0000

@Andreas: Thanks for your comment!

Yes, such little incompatibilities between the databases can be annoying. Hence I prefer to use the same database type in all environments, as it eliminates a possible source of problems.

And yes, setting up a new project is quite smooth, even with MySQL (as soon as you learned about the “-d” option *g*).

By: Andreas

Andreas — Sun, 15 Mar 2009 10:37:35 +0000

When I started learning rails I used SQLite for the development. Works just fine. But there are certain pitfalls with SQLite on your development machine when you’re going to use MySQL in production:
If you use boolean values they are handled differently in SQLite and MySQL (That’s not a big problem because rails handles that for you – unless you use some complex queries as i did :( ). And certain functions are different: For exmple, it’s: RAND() in MySQL but RANDOM() in SQLite.

Just saying this because I spent a lot of time figuring out why my tests aren’t working as expected (development, production: MySQL, test: SQLite)

Well, anyway: I like how easy it is to set up a new project using SQLite.