Yeah rails is fine to do this stuff in. We use migrations because thy make structure maintenance easier especially if your app is deployed in multiple locations (or even just across a deployment an a development machine)
Sent from my iPhone On 29/01/2009, at 4:11 PM, Jay Mcgratgh <[email protected] > wrote: > > remotely related ... > > Can Rails on Ruby work with an established sqlite3 (or mySQL) > database? > the tutorials I have read so far build the sqlite3 tables with the $ > "ruby script/generate model ... " command. > > I guess what I am trying to figure out is if the Ruby Rails platform > will be a wise investment of my time to learn and eventually become > proficient if my goal is to build some web applications that > interact to > already established databases. > > I would prefer to build my database the old fashioned way - e.g., SQL > CREATE statements - and be able to modify the structure on the fly > (structure and data). The web pages would be a simple GUI interface > for > my computer challenged friends! :) > I am hopeful that the Rails on Ruby will allow that flexibility? > Eventually, I suspect that I will be good enough to do it all in Rails > like you all do. > > Advice? > > thanks in advance > > -- > Posted via http://www.ruby-forum.com/. > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
