a taste of ruby on rails

[sde]

i setup ruby on rails on a redhat 9 system tonight. i dove into a beginners tutorial on how to make a cookbook interfacing to mysql.

i setup a new rails app.
i configured the mysql connection info.
i created the table in mysql.
i added what essentially is a new object for a recipe, along with another line of code.

i may be missing a simple step or 2, .. but basically after i tweaked some configs and added a couple lines of code, i had a fully functional editor for recipes. list/edit/add/remove.

it detected the field types and made the appropriate input boxes for each field.

i then added a 'categories' table. my object was named "category" and it knows to associate a 'category' with the 'categories' table. same with the 'recipe' object and the table named 'recipes'

all i could do was laugh. it was sort of amusing and i was thinking that this is cool and all, but it seems like it does too much for me.

well, .. i guess it does too much for you by default .. and then you have to tell it what you want to customize. by the end of the tutorial i can see a bit further into how much more it can be customized .. but i have a feeling i have barely wet my feet.

i'm not 100% sold yet, .. but i'm looking forward to learning more.

here's the tutorial i followed: http://www.onlamp.com/pub/a/onlamp/2...ls.html?page=1

[teknomage1]

I think the point of rails is to push all that db interface code we're so used to writing in php down beyond a level where we need to deal with it. That way we're free to think about whatever problem we're supposed to be solving rather than trying to remember what table holds what data.